Proxy API

Name: Proxy API API
Brand: Proxy API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsPackage RegistryapiKey5 EndpointsREST

For Agents

Forward arbitrary HTTP requests to any Apideck-connected provider's native API using the connection's stored OAuth token, when a Unified API does not cover the operation needed.

Connect the Proxy API to your agent

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

Forward a GET request to a connector's native endpoint via GET /proxy

Forward a POST request with body payload via POST /proxy

Forward PUT, PATCH, and DELETE requests for full HTTP coverage

Reuse the consumer's already-authorised OAuth token without separate auth handling

GET STARTED

Start building with Proxy API API

Explore with Jentic

View OpenAPI Document

Use for: Call a connector-specific endpoint that the Unified API does not cover, Forward a GET request to the underlying provider's API using the stored token, POST a payload to a vendor endpoint without managing the OAuth flow myself, PATCH a resource on the connected provider through Apideck

Not supported: Does not normalise responses, set up new OAuth connections, or trigger Unified API workflows — use only as a pass-through to connector-native endpoints when a Unified API does not cover the operation.

The Apideck Proxy API forwards arbitrary HTTP requests to a connector's underlying API while reusing the OAuth token and configuration that Apideck has already negotiated with the end user. Five endpoints — GET, POST, PUT, PATCH, DELETE — all on the single /proxy path expose the full HTTP surface, with the target service identified by Apideck headers and the path passed through to the upstream provider. It exists as an escape hatch when a Unified API does not cover a feature the agent or product needs to call directly. Authentication uses the Apideck Authorization header plus x-apideck-app-id; the consumer ID identifies which connection the request is forwarded over.

Use Cases

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

★ Provider-Specific Feature Escape Hatch

When a Unified API (CRM, HRIS, Accounting, etc.) does not expose a feature a customer needs — a vendor-specific custom object, a beta endpoint, an unusual report — call the Proxy API instead. The Proxy reuses the connection's already-stored OAuth token, so the agent does not have to manage credentials separately. Useful for filling gaps without abandoning the unified integration model.

Use POST /proxy with x-apideck-service-id 'salesforce' to call /services/data/v58.0/sobjects/CustomObject__c with a JSON body, returning the resulting record ID

Reusing Stored OAuth Tokens

Avoid building a parallel OAuth flow for the few endpoints not covered by Unified APIs. The Proxy API forwards the request using the consumer's stored token, so a product that already integrates Apideck Vault and a Unified API can extend coverage to any endpoint the connector exposes by routing through /proxy.

Forward GET /proxy with x-apideck-service-id 'hubspot' targeting /crm/v3/properties/companies, parse the response, and return all custom property names

Custom Report Pulls

Pull a connector-specific custom report or query that has no Unified API equivalent. POST /proxy carries the request body, the upstream path, and the target service ID, and Apideck applies the connection's auth before forwarding. The response is returned unmodified, so the agent processes the upstream payload directly.

POST /proxy with x-apideck-service-id 'quickbooks' targeting /v3/company/{realmId}/query with a SQL-like query string, return the raw upstream JSON

AI Agent Custom Call via Jentic

An AI agent needs to call a vendor-specific endpoint that no Unified API covers. Through Jentic, the agent searches 'forward request through apideck proxy', loads the matching /proxy operation, and executes it with the upstream path and body. Jentic stores the Apideck Authorization, x-apideck-app-id, and x-apideck-consumer-id headers separately so the agent never holds raw credentials.

Through Jentic, search 'forward request through apideck proxy', load POST /proxy, set x-apideck-service-id and the upstream path, and execute the call with the supplied body

Key Endpoints

5 endpoints — the apideck proxy api forwards arbitrary http requests to a connector's underlying api while reusing the oauth token and configuration that apideck has already negotiated with the end user.

METHOD

PATH

DESCRIPTION

GET

/proxy

Forward a GET request to the connected provider

POST

/proxy

Forward a POST request to the connected provider

PUT

/proxy

Forward a PUT request to the connected provider

PATCH

/proxy

Forward a PATCH request to the connected provider

DELETE

/proxy

Forward a DELETE request to the connected provider

GET

/proxy

Forward a GET request to the connected provider

POST

/proxy

Forward a POST request to the connected provider

PUT

/proxy

Forward a PUT request to the connected provider

PATCH

/proxy

Forward a PATCH request to the connected provider

DELETE

/proxy

Forward a DELETE request to the connected provider

Why though Jentic?

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

Credential isolation

Apideck application keys, x-apideck-app-id, and x-apideck-consumer-id values are stored encrypted in the Jentic vault. Agents receive scoped execution tokens, and the upstream provider's OAuth token never leaves Apideck — the agent never holds either secret.

Intent-based discovery

Agents search by intent (for example 'forward request through apideck proxy' or 'call connector native endpoint') and Jentic returns the matching /proxy operation with its input schema. The agent then supplies the service ID and upstream path at execution time.

Time to first call

Direct Apideck Proxy integration: half a day to wire headers and per-service routing. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Apideck Vault API

Vault stores the OAuth tokens and connection configuration the Proxy reuses on every forwarded request.

Use Vault to set up the connection, then use Proxy when calling endpoints that no Unified API covers.

Complementary

Apideck CRM Unified API

CRM Unified API handles the standard CRM operations; Proxy fills gaps for vendor-specific custom objects.

Use CRM Unified for standard contacts/deals/companies; fall back to Proxy when a customer needs a Salesforce or HubSpot-specific endpoint.

Alternative

Pipedream Connect

Pipedream Connect provides a similar managed-OAuth proxy across thousands of apps with a different trade-off (workflow runtime included).

Choose Pipedream when you also need managed workflow execution; choose Apideck Proxy when sticking with a unified-API-first model.

FAQs

Specific to using Proxy API API through Jentic.

What authentication does the Apideck Proxy API use?

An apiKey scheme on the `Authorization` header with your Apideck application key, plus `x-apideck-app-id` and `x-apideck-consumer-id` headers. The consumer ID identifies which connection the proxy uses, so the underlying provider's OAuth token is already stored at Apideck. Through Jentic these are stored encrypted in the vault and injected at execution.

Can I call any endpoint on a connected provider through the Proxy API?

Yes — the upstream path is passed via Apideck headers and the request body is forwarded as-is for POST, PUT, and PATCH. The Proxy supports GET, POST, PUT, PATCH, and DELETE on /proxy. Use it as a fallback when a Unified API does not cover a feature you need.

What are the rate limits for the Apideck Proxy API?

The OpenAPI spec does not publish per-endpoint rate limits. Apideck applies plan-based limits at unify.apideck.com plus the upstream provider's own limits — Proxy calls count against both. See https://developers.apideck.com for your plan's gateway quota.

How do I forward a request through Jentic?

Install with `pip install jentic`, then run the search query 'forward request through apideck proxy'. Jentic returns the matching /proxy operation (GET/POST/PUT/PATCH/DELETE) — load its schema, set the service ID and upstream path, and execute.

When should I use the Proxy API instead of a Unified API?

Use a Unified API (CRM, HRIS, POS, etc.) whenever it covers the operation — the schema is normalised across providers and the agent does not need to know vendor-specific details. Use Proxy only as an escape hatch for connector-specific endpoints, beta features, or custom objects the Unified API does not yet expose.

Does the Proxy API normalise the response from the underlying provider?

No. The response body is returned unchanged from the upstream provider — the Proxy is a pass-through. Your code or agent must parse the vendor-specific response shape. This is the trade-off for getting access to endpoints not covered by Unified APIs.