API calls for managing and updating custom data sources
Last updated
Was this helpful?
Use these REST API calls to manage and update custom providers and data sources with Open Authorization API.
Creates a custom provider and returns the provider ID.
Lists all configured custom providers.
Returns details for an individual custom provider.
Delete a custom provider by ID.
Return all data sources for a Custom Provider ID.
You can constrain large responses by adding a filter to the request query string. Include the operator (eq), and value, for example:
CURL <VEZA_URL>/api/v1/providers/custom?filter=name eq "GitHub"&order_by=state
Veza expects that spaces in URLS are encoded as "+" (for example?name+eq+"GitHub"&order_by=state). Note that some libraries and clients will encode spaces as "%2B" by default, which will cause errors unless you override this behavior.
Register a new datasource for a custom provider. There can be more than one datasource for a single provider.
Returns details for a single datasource.
Unbind a datasource from a custom provider, and delete it.
To push authorization metadata for a custom datasource, you can specify the source and provider IDs, and upload a payload with the entities and permissions in JSON format.
You can also use the push_csv endpoint to upload CSV data prepared with the expected
CSV Import columns.
A warning is returned if a matching identity can't be found for an IdP principal.
The populated template can be compressed and encoded, for significantly reduced payload size.
Specify the compression_type. Currently supported: GZIP.
If compression is selected, Veza will expect the payload json_data as a compressed, base64-encoded string.
To compress using shell commands:
Size is typically not an issue when updating custom datasources. However, you may want to compress large payloads. The maximum body size is 100MB (compressed or uncompressed).
Veza expects the populated template as a single JSON string, enclosed in the request body json_data field. Any "s and non-ASCII characters must be escaped.
To convert a template to JSON string using Python, the json.dumps() method could be used:
You can optionally add an icon for your custom provider by uploading a PNG or SVG file (less than 64kb) as a base64-encoded string:
Upload a custom icon to display for an OAA provider.
Return the type and string-encoded icon for a custom provider.
Delete the icon associated with an OAA provider.
/api/v1/providers/custom
/api/v1/providers/custom
The maximum number of results to be returned. Fewer results may be returned even when more pages exist.
The token specifying the specific page of results to retrieve.
/api/v1/providers/custom/{id}
/api/v1/providers/custom/{id}
/api/v1/providers/custom/{id}/datasources
The maximum number of results to be returned. Fewer results may be returned even when more pages exist.
The token specifying the specific page of results to retrieve.
/api/v1/providers/custom/{id}/datasources
/api/v1/providers/custom/{id}/datasources/{data_source_id}
/api/v1/providers/custom/{id}/datasources/{data_source_id}
/api/v1/providers/custom/{id}/datasources/{data_source_id}:push
/api/v1/providers/custom/{id}/datasources/{data_source_id}:push_csv
/api/v1/providers/custom/{id}:icon
/api/v1/providers/custom/{id}:icon
/api/v1/providers/custom:icon
/api/v1/providers/custom/{id}:icon