Skip to main content

Certify Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a sync or streaming data flow that sends data to a Certify location.
certify_api.png

Certify

Create a Certify Destination​

  1. Click the + icon on the Nexset that will be sent to the Certify destination, and select the Send to Destination option from the menu.

  2. Select the Certify connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Certify organization, and click Next; or, create a new Certify credential for use in this flow.

  3. In Nexla, Certify destinations can be created using pre-built endpoint templates, which expedite destination setup for common Certify endpoints. Each template is designed specifically for the corresponding Certify endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Certify destinations can also be configured manually, allowing you to send data to Certify endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Certify endpoints. Each template is designed specifically for the corresponding Certify endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Create Department

    This endpoint creates or updates department records for the user's company. For each department element in the POST body, this method will update department records corresponding to the IDs supplied. Any elements where new values were not provided will retain their current value. Use this endpoint when you need to create or update departments from your data sources.

    • The endpoint uses POST requests to https://api.certify.com/v1/departments. The endpoint URL is automatically constructed based on the Certify API base URL.
    • The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the department data to create or update. The request body should follow the Certify API v1 specification for creating or updating departments, including required fields and field names.
    • Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create or update a department. If you need to create or update multiple departments, you can send multiple records, but each will be processed as a separate request.

    The request body must be properly formatted JSON that matches the Certify API v1 specification for creating or updating departments. The endpoint requires API key authentication in the x-api-key and x-api-secret headers, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For department elements where IDs are supplied, the endpoint will update existing records. Any elements where new values were not provided will retain their current value. For detailed information about creating or updating departments, including required fields, field names, and request formats, see the Certify API documentation.

    expensecategories

    This endpoint creates or updates expense category records for the user's company. For each expense category element in the POST body, this method will update expense category records corresponding to the IDs supplied. Any elements where new values were not provided will retain their current value. Use this endpoint when you need to create or update expense categories from your data sources.

    • The endpoint uses POST requests to https://api.certify.com/v1/expensecategories. The endpoint URL is automatically constructed based on the Certify API base URL.
    • The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the expense category data to create or update. The request body should follow the Certify API v1 specification for creating or updating expense categories, including required fields and field names.
    • Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create or update an expense category. If you need to create or update multiple expense categories, you can send multiple records, but each will be processed as a separate request.

    The request body must be properly formatted JSON that matches the Certify API v1 specification for creating or updating expense categories. The endpoint requires API key authentication in the x-api-key and x-api-secret headers, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For expense category elements where IDs are supplied, the endpoint will update existing records. Any elements where new values were not provided will retain their current value. For detailed information about creating or updating expense categories, including required fields, field names, and request formats, see the Certify API documentation.

Configure Manually​

Certify destinations can be manually configured to send data to any valid Certify API v1 endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Certify API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Certify API from the Method pulldown menu. The Certify API v1 primarily uses POST requests for data writing operations. The most common methods are:

    • POST: For creating new resources or updating existing data (e.g., creating departments, updating expense categories)
    • PUT: For updating existing data
    • PATCH: For partial updates to existing data
    • DELETE: For removing data

Data Format​

  1. Select the format in which the Nexset data will be sent to the Certify API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The Certify API v1 typically uses JSON format for request bodies.

API Endpoint URL​

  1. Enter the URL of the Certify API endpoint to which you want to send the Nexset data in the URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Certify API endpoints typically follow the pattern https://api.certify.com/v1/{endpoint_path}.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires API key authentication in the x-api-key and x-api-secret headers, which is handled automatically by your credential configuration. For detailed information about Certify API endpoints and available APIs, see the Certify API documentation.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Additional headers are often required for API versioning, content type specifications, or custom authentication requirements.

    You do not need to include any headers already present in the credentials. Common headers like Authorization (x-api-key and x-api-secret), Content-Type, and Accept are typically handled automatically by Nexla based on your credential configuration. The Certify API v1 requires API key authentication in the x-api-key and x-api-secret headers, which is handled automatically by your credential configuration. The Content-Type: application/json header is typically set automatically for JSON request bodies.

Request Body​

Optional

  • If the API endpoint requires a specific request body format, configure how Nexla should format the request body from your Nexset data. The request body can be sent as JSON, XML, or form data, depending on the API endpoint requirements.

    • For JSON format, select JSON from the Request Body Format dropdown, and the Nexset data will be sent as a JSON object in the request body. Certify API v1 endpoints typically use JSON format for request bodies.

    • For XML format, select XML from the Request Body Format dropdown, and the Nexset data will be converted to XML format in the request body.

    • For Form data format, select Form Data from the Request Body Format dropdown, and the Nexset data will be sent as form-encoded data in the request body.

Save the Destination​

  1. Once all configuration steps have been completed, click the Save button to save your destination configuration.

  2. The destination will now be available in your data flow and will begin sending data to the Certify endpoint according to the configured settings.