Introduction
This integration enables data exchange between Clay and external tools using HTTP API with JWT authentication. It allows users to send data to or retrieve data from any system that supports JWT-based authentication. The integration leverages Clay's HTTP API provider, offering flexibility in data transfer and seamless connectivity with various third-party applications that require secure, token-based authentication methods.
Input
Name | Is Optional | Description | Type |
Location of JWT token in Auth Response | In the JWT token response, each provider puts the token in a different place (i.e. Snov.io calls it access_token). | text | |
Token Type | true | Puts a token type in your authorization header. For instance, if the token is a Bearer token, and you type Bearer, it will add Bearer in front of the token in the header. Defaults to Bearer. | text |
Auth Header Name | true | The name of the Auth Header the API is expecting. Defaults to Authorization. | text |
Method | true | The HTTP method you want to use. Defaults to GET. | text |
Endpoint | Enter the endpoint to send the requests to, e.g. https://httpbin.org/post | url | |
Body | true | Enter the data body to include, e.g. {"a":1, "b": 2} | longtext |
Additional Headers (Optional) | true | Enter any header fields to set, e.g. {'content-type': 'application/json'} | object |
Remove null & undefined values | true | Toggle this field if you want to remove any values that are undefined or null | boolean |
Field Paths to Return | true | If used, we'll only return field paths referenced in this input. You can enter multiple field paths, separated by a comma. For nested parameters, use dot path notation (e.g. object1.object2.name). This field is primarily used for APIs with unpredicatable input length to pull only data you need. | text |