All integrations

ProAbono

BUSINESS · COMMERCE & FINANCE

Customers, subscriptions, offers, usage, and invoices on their own key.

Connect ProAbono with Fabriq Developer

Your user pastes their ProAbono credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.

from af_sdk import AgenticFabriq

af = AgenticFabriq()                      # reads AF_APP_ID / AF_APP_SECRET

url = await af.initiate_connection(request, provider="proabono", method="api_key")
return redirect(url)                      # an AF-hosted page, not yours

async with await af.for_user(request) as session:
    tools = await session.get_tools()     # only what this user granted

Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.

Connecting ProAbono in practice

ProAbono gives every account its own API host — requests go to https://api-{id}.proabono.com rather than a shared endpoint — so nothing is portable between tenants without reconfiguration. Authentication is HTTP Basic with the agent key as username and the API key as password, base64 of "agent_key:api_key", and there are three separate APIs (Live, Backoffice and Backoffice for Platform) to choose between.

Scopes that draw scrutiny

  • agent_key and api_key pair ProAbono documents no scopes and warns that "your API keys carry many privileges, so be sure to keep them secret". Because they are sent as Basic auth, the pair is recoverable from any captured header.

Worth knowing

  • The account id is part of the hostname, so an integration that hardcodes api.proabono.com never reaches anything and a tenant move means a config change.
  • Pagination is HATEOAS-style — Page, SizePage, Count, TotalItems and a Links array with rel of prev or next — rather than a cursor or offset parameter, so a client has to follow links instead of computing them.
  • Content-Type and Accept must both be application/json and HTTPS is required, so a lenient HTTP client that omits Accept can get a response it cannot parse.
  • The billing API is split into Live and Backoffice surfaces, so an agent has to know which one an operation lives on before it can call it.

Checked against ProAbono API reference (2026-09-29), ProAbono documentation (2026-09-29)

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

proabono_get_balancelinesREAD

List balancelines via GET /BalanceLines

api
proabono_get_customerREAD

Retrieve customer via GET /Customer

api
proabono_get_customerbillingaddressREAD

Retrieve customer billing address via GET /CustomerBillingAddress

api
proabono_get_customersREAD

List customers via GET /Customers

api
proabono_get_customersettingspaymentREAD

Retrieve customer payment settings via GET /CustomerSettingsPayment

api
proabono_get_featureREAD

Retrieve feature via GET /Feature

api
proabono_get_featuresREAD

List features via GET /Features

api
proabono_get_invoiceREAD

Retrieve invoice by query via GET /Invoice

api
proabono_get_invoice_by_idinvoiceREAD

Retrieve invoice via GET /Invoice/{IdInvoice}

api
proabono_get_invoicesREAD

List invoices via GET /Invoices

api
proabono_get_offerREAD

Retrieve offer via GET /Offer

api
proabono_get_offersREAD

List offers via GET /Offers

api
proabono_get_subscriptionREAD

Retrieve subscription by customer via GET /Subscription

api
proabono_get_subscription_by_idsubscriptionREAD

Retrieve subscription via GET /Subscription/{IdSubscription}

api
proabono_get_subscriptionsREAD

List subscriptions via GET /Subscriptions

api
proabono_get_usageREAD

Retrieve usage via GET /Usage

api
proabono_get_usagesREAD

List usages via GET /Usages

api
proabono_post_balancelineWRITE

Create balanceline via POST /BalanceLine

api
proabono_post_billing_customerWRITE

Bill customer via POST /Billing/Customer

api
proabono_post_customerWRITE

Create or update customer via POST /Customer

api
proabono_post_customer_anonymizationWRITE

Anonymize customer via POST /Customer/Anonymization

api
proabono_post_customer_by_idcustomer_invalidationWRITE

Invalidate customer by id via POST /Customer/{idCustomer}/Invalidation

api
proabono_post_customer_by_idcustomer_suspensionWRITE

Suspend customer by id via POST /Customer/{idCustomer}/Suspension

api
proabono_post_customer_invalidationWRITE

Invalidate customer via POST /Customer/Invalidation

api
proabono_post_customer_linksrevokationWRITE

Revoke customer crypted links via POST /Customer/LinksRevokation

api
proabono_post_customer_suspensionWRITE

Suspend customer via POST /Customer/Suspension

api
proabono_post_customerbillingaddressWRITE

Update customer billing address via POST /CustomerBillingAddress

api
proabono_post_customersettingspaymentWRITE

Update customer payment settings via POST /CustomerSettingsPayment

api
proabono_post_pricing_balancelineREAD

Quote balanceline via POST /Pricing/BalanceLine

api
proabono_post_pricing_subscriptionREAD

Quote subscription via POST /Pricing/Subscription

api
proabono_post_pricing_subscription_by_idsubscription_startREAD

Quote subscription start via POST /Pricing/Subscription/{IdSubscription}/Start

api
proabono_post_pricing_subscription_by_idsubscription_upgradeREAD

Quote subscription upgrade via POST /Pricing/Subscription/{IdSubscription}/Upgrade

api
proabono_post_pricing_usageREAD

Quote usage update via POST /Pricing/Usage

api
proabono_post_subscriptionWRITE

Create subscription via POST /Subscription

api
proabono_post_subscription_by_idsubscription_datetermWRITE

Update subscription term date via POST /Subscription/{IdSubscription}/DateTerm

api
proabono_post_subscription_by_idsubscription_startWRITE

Start subscription via POST /Subscription/{IdSubscription}/Start

api
proabono_post_subscription_by_idsubscription_suspensionWRITE

Suspend subscription via POST /Subscription/{IdSubscription}/Suspension

api
proabono_post_subscription_by_idsubscription_terminationWRITE

Terminate subscription via POST /Subscription/{IdSubscription}/Termination

api
proabono_post_subscription_by_idsubscription_upgradeWRITE

Upgrade subscription via POST /Subscription/{IdSubscription}/Upgrade

api
proabono_post_usageWRITE

Update usage via POST /Usage

api
proabono_post_usagesWRITE

Update multiple usages via POST /Usages

api

Put ProAbono behind one governed endpoint.

Same permissions, same audit trail, whatever else you connect next.