FawryPay API

Name: FawryPay API
Brand: FawryPay API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey3 EndpointsREST

For Agents

Authenticate against FawryPay and retrieve payment resource configurations needed to charge customers across Egypt's Fawry network.

Install Jentic One Beta

Connect the FawryPay API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FawryPay 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 FawryPay API.

Exchange credentials for a short-lived access token via /auth/token

List payment resources available to a merchant account

Retrieve a single resource record by identifier

Bridge Egyptian card, wallet, and Fawry-agent payments into agent workflows

GET STARTED

Start building with FawryPay API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use FawryPay API for, with concrete tasks.

★ Egyptian Checkout Integration

Merchants selling into Egypt use FawryPay to accept card payments, mobile wallets, and cash via Fawry's offline agent network. The API issues an access token through /auth/token and then exposes the resources a merchant has configured, which a backend reads before constructing payment requests. This lets a small storefront integrate Egypt's most-used payment rail without building agent-network logic from scratch.

Call POST /auth/token with merchant credentials, then GET /resources to list configured FawryPay payment methods for the account.

Resource Configuration Lookup

Operations teams managing multiple FawryPay merchant accounts need to inspect which resources are provisioned. The GET /resources and GET /resources/{id} endpoints return the configured payment products and identifiers so internal tooling can reconcile billing setups, surface configuration drift, or back-fill missing IDs in an order management system.

Authenticate and call GET /resources/{id} for each configured Fawry resource ID stored in the internal merchant database.

Agent-Driven Egyptian Payment Onboarding

An AI agent helping a Cairo-based merchant onboard onto FawryPay can use Jentic to discover the auth and resources operations, exchange credentials for a token, and validate that the merchant has at least one resource configured before a customer-facing checkout goes live. The agent runs the full validation in a single Jentic-managed session without storing the raw API key.

Use Jentic to search 'authenticate fawrypay merchant', execute POST /auth/token, then run GET /resources and confirm at least one resource entry is returned.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for fawrypay api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/auth/token

Exchange credentials for an access token

GET

/resources

List configured payment resources

GET

/resources/{id}

Retrieve a single payment resource by ID

POST

/auth/token

Exchange credentials for an access token

GET

/resources

List configured payment resources

GET

/resources/{id}

Retrieve a single payment resource by ID

Why Jentic?

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

Credential isolation

FawryPay API keys are stored encrypted in the Jentic vault. Agents call /auth/token through Jentic and receive only the resulting scoped access token, never the raw X-API-Key.

Intent-based discovery

Agents search by intent (e.g. 'authenticate fawrypay merchant') and Jentic returns the matching FawryPay operation with its input schema, so the agent can call POST /auth/token without browsing docs.

Time to first call

Direct FawryPay integration: 1-3 days for credential exchange, error handling, and resource lookup. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using FawryPay API through Jentic.

Why is there no official OpenAPI spec for FawryPay API?

FawryPay does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call FawryPay API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the FawryPay API use?

The FawryPay API uses an API key passed in the X-API-Key header to call POST /auth/token, which returns a short-lived access token used on subsequent requests. Through Jentic the raw X-API-Key is held in the vault so agents only ever see scoped tokens.

Can I list all payment resources on my FawryPay account?

Yes. GET /resources returns the payment resources configured for the authenticated merchant, and GET /resources/{id} returns a single resource by its identifier.

What are the rate limits for the FawryPay API?

FawryPay does not publish per-endpoint rate limits in the spec; production limits are set per merchant contract. Apply exponential backoff on 429 responses and contact FawryPay support for documented thresholds.

How do I authenticate against FawryPay through Jentic?

Run pip install jentic, then search 'authenticate fawrypay merchant', load the POST /auth/token operation, and execute it with credentials sourced from the Jentic vault to receive an access token.

Does FawryPay support recurring billing?

This spec exposes authentication and resource lookup only; recurring billing is configured server-side by FawryPay and is not represented as endpoints in this OpenAPI definition.