Relay an Apify POST | NativePort

Hands the call to https://api.apify.com/{path}, rewriting Authorization to the secret Apify token; a client-sent token query param is discarded. This is how actors and tasks run through the run-sync endpoints.

Authentication

AuthorizationBearer

Your per-client bearer token — the API key the gateway issued to you. Present it in Authorization: Bearer <token> form. A token that is missing, unknown, or revoked draws a 401. Before the call is sent upstream the token is removed (stripped, or swapped for the upstream’s own credential); it never makes it past the gateway.

Path parameters

pathstringRequired

The path to call on the Apify API, / segments included — all of it after /apify/ is passed to https://api.apify.com/ when the allowlist admits it. Only run-sync actions get in, e.g. v2/acts/{actorId}/run-sync-get-dataset-items or v2/actor-tasks/{actorTaskId}/run-sync. {actorId} must be one tilde-form segment (e.g. apify~web-scraper).

The path to call on the Apify API, `/` segments included — all of it after `/apify/` is passed to `https://api.apify.com/` when the allowlist admits it. Only run-sync actions get in, e.g. `v2/acts/{actorId}/run-sync-get-dataset-items` or `v2/actor-tasks/{actorTaskId}/run-sync`. `{actorId}` must be one tilde-form segment (e.g. `apify~web-scraper`).

Request

This endpoint expects a map from strings to any.

Response

Whatever the upstream answered, relayed as-is (status, headers, body). Rendered here as JSON; the true shape is the upstream provider’s to define.

Errors

401

Unauthorized Error

404

Not Found Error

$	curl -X POST https://api.nativeport.ai/apify/v2%2Facts%2Fapify~website-content-crawler%2Frun-sync-get-dataset-items \
>	-H "Authorization: Bearer <token>" \
>	-H "Content-Type: application/json" \
>	-d '{}'

1	{
2	"organic": [
3	{
4	"link": "https://www.apple.com/",
5	"position": 1,
6	"title": "Apple"
7	}
8	],
9	"searchParameters": {
10	"q": "apple inc",
11	"type": "search"
12	}
13	}