Generic REST / OpenAPI
Connect Generic REST / OpenAPI to the rest of your business, with the right person approving what changes and a record of every action.
3 ways to read, 3 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Generic REST / OpenAPI, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create Custom Api OperationApproval by rule
- List Custom Api OperationRead
Example flow
- Generic REST / OpenAPI · List Custom Api OperationDone
- Generic REST / OpenAPI · Create Custom Api OperationNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Generic REST / OpenAPI.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Generic REST / OpenAPI
- Generic REST / OpenAPI's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Connect your own APIs to governed integration flows.
Nexra API definitions API docs- Source actions
- 3
- Destination actions
- 3
- Data type
- 1
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Custom API operation6
- Bulk Read Custom Api OperationSource
Bulk Read operation for Custom Api Operation.
- Create Custom Api OperationDestinationNexra idempotency keyApproval before production
Create operation for Custom Api Operation.
- List Custom Api OperationSource
List operation for Custom Api Operation.
- Search Custom Api OperationSource
Search operation for Custom Api Operation.
- Update Custom Api OperationDestinationNexra idempotency keyApproval before production
Update operation for Custom Api Operation.
- Upsert Custom Api OperationDestinationNexra idempotency keyApproval before production
Upsert operation for Custom Api Operation.
Access and limits
- Authentication
- configured per api definition
Before you build a flow
- Only operations pinned to a validated Nexra API definition and approved HTTPS host can execute.
Developer reference
- Create the Nexra API definitions credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Generic REST / OpenAPI, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/generic-rest-openapi and the Connections API.