Connectors

HTTP REST API source

Read JSON records from an HTTPS API into a SQIP topic

Use the HTTP REST API source when SQIP should regularly request an API and publish the returned JSON records to a topic.

Before you begin

Ask the API owner for:

  • The HTTPS endpoint URL.
  • The authentication method and credentials, if required.
  • A sample JSON response.
  • The API's pagination details, if it returns multiple pages.
  • A stable ID field for each record, such as id or orderId.

Warning

The endpoint must use https://. If it is only reachable on a private company network, ask your SQIP administrator to approve the endpoint.

Example response

The following API response contains records under items, uses id as the record key, and supplies the cursor for the next request in nextCursor.

{
  "items": [
    { "id": "order-42", "status": "paid" },
    { "id": "order-43", "status": "pending" }
  ],
  "nextCursor": "page-002"
}

For this response, enter /items, /id, and /nextCursor in the corresponding JSON Pointer fields.

Install the connector

Select the connector

In Connectors, find HTTP REST API Source and select Select and install.

Choose the output

Enter an installation name, select the tenant, cluster, and namespace, and choose the output topic that will receive the API records.

Configure the API

Complete every field using the table below. Keep the recommended values unless the API owner has given you different requirements.

Add authentication

If authentication is required, select the correct authentication type and enter the credential only in SQIP's credential section.

Install and verify

Review the settings, select Install connector, and wait for Running. Confirm that records appear in the selected output topic.

Configuration fields

FieldWhat to enterExampleRequired
URLThe complete HTTPS endpoint to requesthttps://api.example.com/v1/ordersYes
Auth TypeNONE, BEARER, BASIC, or API_KEYBEARERNo; defaults to NONE
Auth Header NameThe header used for API_KEY authenticationX-API-KeyOnly for API_KEY
Pagination ModeCURSOR when the API returns a next cursor; otherwise NONECURSORNo; defaults to CURSOR
Cursor Query ParameterThe query parameter used to send the current cursorcursorFor CURSOR mode
Initial CursorThe starting cursor supplied by the API owner; otherwise leave blankLeave blankNo
Records JSON PointerThe location of the records in the JSON response; leave blank when the response itself is an array or record/itemsNo; defaults to /items
Key JSON PointerA stable identifier inside each record/idNo, but recommended
Next Cursor JSON PointerThe location of the next cursor in the response/nextCursorFor CURSOR mode
Poll Interval MsHow long SQIP waits between successful requests30000No
Connect Timeout MsHow long SQIP waits to establish a connection5000No
Request Timeout MsMaximum time allowed for one API request10000No
Max Response BytesLargest accepted API response, in bytes5242880 (5 MiB)No
Max Records Per PollLargest number of records accepted in one response1000No
Require JSON Content TypeSelect Yes to require the API to identify its response as JSONYesNo
ParallelismNumber of connector instances1Yes; fixed at 1

Info

A JSON Pointer starts with / and follows the field names in the response. For example, /data/orders selects orders inside data. JSON Pointer is not the same as JSONPath, so do not enter values such as $.items.

Authentication choices

Auth TypeWhen to use itCredential input
NONEThe API is public and requires no loginNone
BEARERThe API expects an access tokenToken
BASICThe API expects a username and passwordUsername and password
API_KEYThe API expects a key in a named headerAPI key and Auth Header Name

Enter only the credential fields required by the selected authentication type. Alternatively, expand Use an existing secret reference instead and enter the approved secret name. Do not use both approaches.

Public test example

You can use this credential-free endpoint to verify a new SQIP environment.

FieldInput
URLhttps://jsonplaceholder.typicode.com/posts
Auth TypeNONE
Auth Header NameX-API-Key
Pagination ModeNONE
Cursor Query Parametercursor
Initial CursorLeave empty
Records JSON PointerLeave empty
Key JSON Pointer/id
Next Cursor JSON Pointer/nextCursor
Poll Interval Ms30000
Connect Timeout Ms5000
Request Timeout Ms10000
Max Response Bytes5242880
Max Records Per Poll1000
Require JSON Content TypeYes

Warning

The public test endpoint returns the same records on every poll. Use it only for a short test, then pause or delete the connector.

If installation fails

  • Confirm that the URL starts with https:// and contains no username, password, token, or API key.
  • Confirm that each JSON Pointer matches the capitalization and nesting in the actual response.
  • In CURSOR mode, confirm that every non-empty response supplies a new cursor.
  • Increase the response or record limit only when the expected response genuinely exceeds it.