Skip to main content

Everhour 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 an Everhour location.
everhour_api.png

Everhour

Create an Everhour Destination​

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

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

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

    Everhour destinations can also be configured manually, allowing you to send data to Everhour 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 Everhour endpoints. Each template is designed specifically for the corresponding Everhour 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 Project

    This endpoint creates a new project resource. Use this endpoint when you need to create new projects in your Everhour account from your data sources.

    • This endpoint automatically creates projects in your Everhour account. No additional configuration is required beyond selecting this endpoint template.
    • The endpoint uses POST requests to https://api.everhour.com/projects. The endpoint URL is automatically constructed based on the Everhour 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 project data to create. The request body should follow the Everhour API specification for creating projects, 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 a project. If you need to create multiple projects, 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 Everhour API specification for creating projects. The endpoint requires API Key authentication via the X-Api-Key header, 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 detailed information about creating projects, including required fields, field names, and request formats, see the Everhour API documentation.

    Create Invoice

    This endpoint creates an invoice. Use this endpoint when you need to create new invoices in your Everhour account from your data sources.

    • Enter the Client ID for which you want to create the invoice in the Client ID field. This is the unique identifier of the client for which you want to create the invoice.

    • The endpoint uses POST requests to https://api.everhour.com/clients/{client_id}/invoices where {client_id} is the Client ID you provide. The endpoint URL is automatically constructed based on the Everhour API base URL and the client ID.
    • 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 invoice data to create. The request body should follow the Everhour API specification for creating invoices, 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 an invoice. If you need to create multiple invoices, you can send multiple records, but each will be processed as a separate request.

    Client IDs can be obtained from other Everhour API endpoints, such as the "Get all invoices" data source endpoint, which may include client information. The request body must be properly formatted JSON that matches the Everhour API specification for creating invoices. The endpoint requires API Key authentication via the X-Api-Key header, 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 detailed information about creating invoices, including required fields, field names, and request formats, see the Everhour API documentation.

Configure Manually​

Everhour destinations can be manually configured to send data to any valid Everhour API 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 Everhour 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 Everhour API from the Method pulldown menu. The Everhour API primarily uses POST requests for data writing operations. The most common methods are:

    • POST: For creating new resources or performing actions (e.g., creating projects, creating invoices)
    • 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 Everhour API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The Everhour API typically uses JSON format for request bodies.

API Endpoint URL​

  1. Enter the URL of the Everhour 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. Everhour API endpoints typically follow the pattern https://api.everhour.com/{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 via the X-Api-Key header, which is handled automatically by your credential configuration. For detailed information about Everhour API endpoints and available APIs, see the Everhour 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, Content-Type, and Accept are typically handled automatically by Nexla based on your credential configuration. The Everhour API requires API Key authentication via the X-Api-Key header, 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. Everhour API 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 Everhour endpoint according to the configured settings.