Skip to content
Get an API key

Get started

Updated

Clients and SDKs

Which clients work against the helping.io API, and how to point one at it.

This API serves the Responses API, so an OpenAI Responses client works against it once you change the base URL and the key. If your app uses Chat Completions, migrate it to Responses first and it will work here unchanged.

The API’s compatibility promise is that the official OpenAI SDKs and Open Responses clients can call it and parse the result without a custom integration: a non-streaming create, a next turn through previous_response_id, a stream read by the SDK’s own event reader, the function-calling loop, and the Conversations API all work the way they do against OpenAI. What is deliberately missing is listed under Not implemented, and nothing else is.

Point the client’s base URL at https://api.helping.io/v1 and use your sk_ key as the API key. The examples on these pages read the key from the HELPINGIO_API_KEY environment variable; see API keys to create one.

Every request sends the key as a bearer token to the same base URL:

Terminal window
curl https://api.helping.io/v1/models \
-H "Authorization: Bearer $HELPINGIO_API_KEY"

The Node and Python examples on the other pages use a client built this way.

A Chat Completions app needs migrating first. This API speaks the Responses API, so /v1/chat/completions answers a 404 today. OpenAI’s guide on moving to Responses covers the changes, and the same code works here once migrated.

POST /v1/chat/completions
{
"error": {
"code": "resource_not_found",
"message": "Unknown request URL: /v1/chat/completions. This surface serves /v1/responses, /v1/conversations and /v1/models (Open Responses). Chat Completions is not supported.",
"param": null,
"type": "not_found_error"
}
}