What authentication does the Apto Payments Card Issuance API use?

Apto Payments uses HTTP bearer authentication. The bearer token is sent in the Authorization header on every request. Through Jentic, the bearer token is stored encrypted in the vault and never enters the agent's context.

Can I issue a physical debit card with this API?

Yes. Call POST /cards with a valid cardholder_id and card configuration; Apto handles the BIN sponsor and network-side issuance. After delivery, call POST /cards/{card_id}/activate to make the card live.

How do I list transactions for a specific card?

Call GET /cards/{card_id}/transactions with the card identifier returned by the issuance step. The endpoint returns the transaction stream that has posted against that card.

What are the rate limits for the Apto Payments API?

The OpenAPI spec does not define explicit rate limits. Apto Payments enforces programme-level limits negotiated as part of your card-issuing agreement; check your Apto contract or programme manager for the exact thresholds.

How do I issue a card through Jentic?

Install Jentic with pip install jentic, search for 'issue a debit card to a new cardholder', load the schemas for POST /cardholders and POST /cards, then execute both calls in sequence. Jentic resolves the bearer token automatically.

Can I limit what my agent is allowed to do with the Apto Payments Card Issuance API?

Yes. Because you run Jentic One yourself, your own rules decide which Apto operations and credentials the agent may use. Apto puts the cardholder and card ids in the URL path (/cardholders/{cardholder_id}, /cards/{card_id}), so a rule can pin the agent to a single card and let it only read that card and call GET /cards/{card_id}/transactions. You pick the operations it may invoke, so state-changing calls such as POST /cards/{card_id}/activate or POST /cards stay off-limits unless you explicitly allow them.