HTTP Gateway

Use Nimbipost from services that do not run TypeScript directly.

The Gateway keeps platform credentials, session bootstrap, request signing, and pagination inside a Node process while other backends call stable HTTP routes.

View Gateway routes Browse adapters

Gateway workflow.

Build once, start the Gateway, then call platform-neutral routes from any backend.

gateway Shell

npm run build
X_AUTH_TOKEN=your_auth_token NIMBIPOST_PORT=4334 npm run start:gateway

Stable routes.

The route shape mirrors the shared adapter contract for users, posts, and search.

routes HTTP

GET /health
GET /v1/:platform/users/:username
GET /v1/:platform/users/:username/posts?total=20
GET /v1/:platform/posts/:postId
GET /v1/:platform/search?q=BTC

Where the Gateway helps.

Use the Gateway when the SDK should be centralized instead of embedded into every service.

Credential boundary

Keep platform tokens and session details in one Node service instead of passing them to clients.

Language-neutral access

Go, Python, Ruby, Java, and other services can call the same adapter layer over HTTP.

Shared pagination

Expose consistent paging behavior even when each upstream platform uses different cursors.

Adapter expansion

Add platform adapters in TypeScript without changing every consuming backend.

Start with the supported adapters.

The Gateway depends on the same adapter registry as the SDK. Review the platform adapter list before choosing credentials and deployment settings.

Open adapter list