Developer API

Name: Developer API API
Brand: Developer API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment Processingbasic28 EndpointsREST

For Agents

Programmatically create an access token, create a pix qr code. Covers 28 operations with basic authentication.

Use for: I need to an access token, I want to a pix qr code, Search for all pix qr codes, Find all a pix qr code

Connect the Developer API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Developer API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Developer API API.

Create an Access Token

List all Pix QR Codes

Retrieve a Pix QR Code

Query and filter Developer API records by parameters

Monitor Developer API operational status and events

GET STARTED

Start building with Developer API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Developer API API for, with concrete tasks.

★ Payments Operations

Use the Developer API to perform payments operations programmatically. The API provides 28 endpoints covering core functionality including create an access token, create a pix qr code, list all pix qr codes.

Call POST /access-tokens to create an access token

Automated Recipient Management

Automate recipient operations by combining multiple Developer API endpoints. Agents can create a pix qr code and then list all pix qr codes in a single workflow.

Call POST /pix-qrcode-payments to create a pix qr code, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Developer API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Search Jentic for 'create an access token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

28 endpoints — at sqala, we believe that everyone deserves access to financial services, and we are committed to providing secure and reliable payment solutions to clients who may have been overlooked by traditional financial institutions.

METHOD

PATH

DESCRIPTION

POST

/access-tokens

Create an Access Token

POST

/pix-qrcode-payments

Create a Pix QR Code

GET

/pix-qrcode-payments

List all Pix QR Codes

GET

/pix-qrcode-payments/{id}

Retrieve a Pix QR Code

POST

/itp-payments

Create an ITP

GET

/itp-payments

List all ITPs

GET

/itp-payments/{id}

Retrieve an ITP

POST

/boleto-payments

Create a Boleto

POST

/access-tokens

Create an Access Token

POST

/pix-qrcode-payments

Create a Pix QR Code

GET

/pix-qrcode-payments

List all Pix QR Codes

GET

/pix-qrcode-payments/{id}

Retrieve a Pix QR Code

POST

/itp-payments

Create an ITP

GET

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Developer API basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create an access token') and Jentic returns the matching Developer API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Developer API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Alternative payments API

Choose Stripe when you need a different approach to payments operations

Alternative

Adyen

Alternative payments API

Choose Adyen when you need a different approach to payments operations

Complementary

Square

Complementary payments API

Choose Square when you need a complementary approach to payments operations

Complementary

Paypal

Complementary payments API

Choose Paypal when you need a complementary approach to payments operations

FAQs

Specific to using Developer API API through Jentic.

What authentication does the Developer API use?

The Developer API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I create an access token with the Developer API?

Yes. Use the POST /access-tokens endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Developer API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create an access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create an access token'. Jentic returns the matching Developer API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Developer API have?

The Developer API exposes 28 endpoints covering recipient, boleto, qrcode operations.