Afosto API

Name: Afosto API
Brand: Afosto API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontbearer16 EndpointsREST

For Agents

Authenticate Afosto users via OAuth, manage instant search indexes and documents, and configure QuicQ CDN proxies for a Dutch commerce stack.

Install Jentic One Beta

Connect the Afosto API to your agent

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

Initiate OAuth authorization sessions and exchange authorization codes for access tokens

Create and manage instant search indexes with configurable analyzers and settings

Bulk-upsert documents into search indexes for product and content discovery

GET STARTED

Start building with Afosto API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Afosto API for, with concrete tasks.

★ Headless Commerce Search

Power product and content search on a headless Afosto storefront by uploading catalog documents to an Instant Search index and querying it from the frontend. Index aliases let you rebuild indexes in the background and atomically swap them in, keeping search latency stable. Typical merchants run thousands of products through a small number of indexes with locale-specific settings.

Create an instant search index named 'products-nl', bulk upsert 500 product documents, then run a search for 'fietshelm' against the index alias and return the top 10 hits

OAuth Identity for Storefront Apps

Use Afosto's OAuth endpoints to authorize storefront and back-office users, obtain bearer tokens, and call the rest of the platform on their behalf. The session authorize flow supports SPA and mobile clients that need short-lived sessions, while the standard authorize endpoint covers server-side exchanges. All subsequent index and proxy calls reuse the same bearer token.

Exchange an authorization code at POST /oauth/authorize for a bearer token, then call GET /instant/indexes with that token to confirm the session is active

CDN Proxy Automation

Manage QuicQ CDN proxy configurations from infrastructure-as-code pipelines instead of the Afosto dashboard. The Proxies endpoints let an agent enumerate existing routes, register new ones for media subdomains, and update cache settings without manual UI work. Useful when spinning up new locales or campaign sites.

List all Afosto QuicQ proxies, then add a new proxy for the subdomain 'cdn-promo.example.com' pointing at the campaign asset bucket

AI Agent Storefront Operations

Through Jentic, an agent can run end-to-end Afosto storefront tasks — refreshing search indexes, rotating aliases, and adjusting CDN proxies — by searching for the operation it needs and executing the call without storing the merchant's bearer token in its context. Jentic handles the OAuth secret in the vault and returns scoped credentials per call.

Search Jentic for 'reindex afosto products', load the documents upsert schema, and execute a refresh of the live product index

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/oauth/authorize

Authorize a user and obtain an access token

POST

/oauth/session/authorize

Start an OAuth session authorization flow

GET

/instant/indexes

List instant search indexes

POST

/instant/indexes/{id}/documents

Upsert documents into a search index

POST

/instant/search/{id}

Run a search query against an index

GET

/instant/search/indexes/{alias}

Resolve an index alias for live search

POST

/oauth/authorize

Authorize a user and obtain an access token

POST

/oauth/session/authorize

Start an OAuth session authorization flow

GET

/instant/indexes

List instant search indexes

POST

/instant/indexes/{id}/documents

Upsert documents into a search index

POST

/instant/search/{id}

Run a search query against an index

Why Jentic?

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

Credential isolation

Afosto bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped, short-lived tokens at execution time — the long-lived OAuth refresh token never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'reindex afosto products') and Jentic returns the matching Afosto operation with its input schema, so the agent can call the right endpoint without browsing Afosto docs.

Time to first call

Direct Afosto integration: 1-2 days to wire up OAuth, indexes, and proxies. Through Jentic: under an hour — search, load schema, execute.

FAQs

Specific to using Afosto API through Jentic.

Why is there no official OpenAPI spec for Afosto API?

Afosto does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Afosto 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 Afosto API use?

The Afosto API uses HTTP bearer tokens. Obtain a token by exchanging an authorization code at POST /oauth/authorize, then send it as Authorization: Bearer <token> on every subsequent call. Through Jentic, the bearer token is stored encrypted in the credential vault and never enters the agent's context.

Can I run product search against an Afosto index with this API?

Yes. Use POST /instant/search/{id} to query a specific index by id, or GET /instant/search/indexes/{alias} to resolve and search through a stable alias. Documents are loaded via POST /instant/indexes/{id}/documents in batches.

What are the rate limits for the Afosto API?

Afosto does not document fixed rate limits in the public spec. Treat the API as standard SaaS — back off on HTTP 429 responses and inspect Retry-After. For high-volume reindex jobs, batch document upserts rather than one-by-one calls.

How do I reindex an Afosto product catalog through Jentic?

Search Jentic for 'upsert afosto documents', load the schema for POST /instant/indexes/{id}/documents, and execute the call with your batch of product records. After indexing, repoint the alias via the indexes endpoint so live search traffic switches over.

Can I manage Afosto QuicQ CDN proxies from code?

Yes. The Proxies group exposes endpoints to list, create, and update CDN proxy routes, so you can manage QuicQ from CI/CD or an agent rather than the Afosto dashboard.

Afosto API

Connect the Afosto API to your agent

Capabilities

Start building with Afosto API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs