Skip to content
Changelog

Report a bug

Elorus integration: operations for AI agents

Elorus connects to Type.com as an integration. This page lists the 333 operations documented for Claude and Codex in Type.com: 136 read, 92 write, 105 destructive.

About Elorus

Elorus is an online invoicing and time-tracking software designed for freelancers and small businesses to manage their finances and projects efficiently.

Categories: Finance & Accounting, Documents & Forms

How to connect Elorus to Type.com

Access
Organization connection: one shared account for the workspace.

To add the connection, follow the steps in Space connections.

Documented operations

333 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.

333 operations listed.

Bills

  • Read

    /v1.2/bills/

    Get the list of bills. --- The response does not include all the bill details. To retrieve more information about a specific bill, use the single bill endpoint.

  • Read

    /v1.2/bills/{id}/

    Get a single bill. --- Returns all available information for a specific bill.

  • Read

    /v1.2/bills/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Read

    /v1.2/bills/{id}/pdf/

    Get the document as PDF. --- Only self-billed invoices will be printed out to PDF.

  • Read

    /v1.2/bills/{parentpk}/attachments/

    Get the list of attachments. --- The list of attachments for the specified record.

  • Read

    /v1.2/bills/{parentpk}/attachments/{id}/

    Get a single attachment. ---

  • Read

    /v1.2/bills/{parentpk}/attachments/{id}/file/

    Get the actual attachment file. --- This endpoint may return a 307 redirect response. To retrieve the file you should follow the redirection.

  • Read

    /v1.2/bills/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Read

    /v1.2/bills/{parentpk}/sent-email-messages/

    Get the list of tracked email messages for this document. --- Messages are ordered by most recent first.

  • Write

    /v1.2/bills/

    Create a new bill. --- To create a new bill, you must first specify the supplier. If you do not specify the currency code, the supplier's default currency will have a higher priority than your base currency.

  • Write

    /v1.2/bills/{id}/

    Partially update a bill. --- Since this method does not modify the line items and amounts you can always use it regardless the bill status. On the other hand, the full update action is only applicable to draft bills.

  • Write

    /v1.2/bills/{id}/email-from-template/

    The subject and message are rendered from the template resolved via templateid, or the organization's default template if not provided.

  • Write

    /v1.2/bills/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Write

    /v1.2/bills/{parentpk}/attachments/

    Create a new attachment. --- Adds a new attachment to the specified record. The actual attachment file must be sent within the request body. Incoming data must be encoded as multipart/form-data.

  • Write

    /v1.2/bills/{parentpk}/attachments/{id}/

    Partially update an attachment. --- You may change the attachment title, but you cannot replace the actual file.

  • Write

    /v1.2/bills/{parentpk}/notes/

    Create a new private note. ---

  • Destructive

    /v1.2/bills/{id}/

    Update a bill. --- You must send all required fields for the record to be successfully updated. You may only modify draft bills. To update issued bills, you should first mark them as draft via the partial update endpoint.

  • Destructive

    /v1.2/bills/{id}/

    Delete a bill. --- Note that you cannot delete bills marked as issued (i.e. the draft field is set to false).

  • Destructive

    /v1.2/bills/{id}/void/

    Mark the document as void or convert it from "void" back to "issued". Notice that when you mark a document as void: It must already be issued. It remains in the system for future reference, but is not involved in Elorus reports.

  • Destructive

    /v1.2/bills/{parentpk}/attachments/{id}/

    Delete an attachment. ---

  • Destructive

    /v1.2/bills/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/bills/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

Cashpayments

  • Read

    /v1.2/cashpayments/

    Get the list of payments sent. ---

  • Read

    /v1.2/cashpayments/{id}/

    Get a single payment sent. --- Returns all available information for a specific payment sent.

  • Read

    /v1.2/cashpayments/{id}/pdf/

    Get the document as PDF. --- Download the document in PDF file format.

  • Read

    /v1.2/cashpayments/{parentpk}/attachments/

    Get the list of attachments. --- The list of attachments for the specified record.

  • Read

    /v1.2/cashpayments/{parentpk}/attachments/{id}/

    Get a single attachment. ---

  • Read

    /v1.2/cashpayments/{parentpk}/attachments/{id}/file/

    Get the actual attachment file. --- This endpoint may return a 307 redirect response. To retrieve the file you should follow the redirection.

  • Read

    /v1.2/cashpayments/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Write

    /v1.2/cashpayments/

    Create a new payment sent. --- Whenever you send money to suppliers or clients (e.g., to pay a supplier invoice), you can create a “Payment sent” record to represent the transaction. Payments sent are divided into three types: Supplier Payment Client Refund Other payment

  • Write

    /v1.2/cashpayments/{parentpk}/attachments/

    Create a new attachment. --- Adds a new attachment to the specified record. The actual attachment file must be sent within the request body. Incoming data must be encoded as multipart/form-data.

  • Write

    /v1.2/cashpayments/{parentpk}/attachments/{id}/

    Partially update an attachment. --- You may change the attachment title, but you cannot replace the actual file.

  • Write

    /v1.2/cashpayments/{parentpk}/notes/

    Create a new private note. ---

  • Destructive

    /v1.2/cashpayments/{id}/

    Update a payment sent. --- When updating credit note or bill payments , you will not be able to change the associated contact or the currency code. In addition, the transaction type cannot be modified.

  • Destructive

    /v1.2/cashpayments/{id}/

    Delete a payment sent. --- Deleting a bill payment may result in changing the bill's status. For example, if the bill was marked as 'paid' it will now revert to 'issued' or 'partially paid'.

  • Destructive

    /v1.2/cashpayments/{parentpk}/attachments/{id}/

    Delete an attachment. ---

  • Destructive

    /v1.2/cashpayments/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/cashpayments/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

Cashreceipts

  • Read

    /v1.2/cashreceipts/

    Get the list of payments received. --- The response does not include all the payments received details. To retrieve more information about a specific payment received, use the single payments received endpoint.

  • Read

    /v1.2/cashreceipts/{id}/

    Get a single payment received. --- Returns all available information for a specific payment received.

  • Read

    /v1.2/cashreceipts/{id}/pdf/

    Get the document as PDF. --- Download the document in PDF file format.

  • Read

    /v1.2/cashreceipts/{parentpk}/attachments/

    Get the list of attachments. --- The list of attachments for the specified record.

  • Read

    /v1.2/cashreceipts/{parentpk}/attachments/{id}/

    Get a single attachment. ---

  • Read

    /v1.2/cashreceipts/{parentpk}/attachments/{id}/file/

    Get the actual attachment file. --- This endpoint may return a 307 redirect response. To retrieve the file you should follow the redirection.

  • Read

    /v1.2/cashreceipts/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Write

    /v1.2/cashreceipts/

    Create a new payment received. --- Please notice that in invoicepayments array the "amount" stands for the amount of money that you assigned to that specific invoice from the payment received "amount" field, and it does not refer to the invoice total cost, since Elorus already k…

  • Write

    /v1.2/cashreceipts/{parentpk}/attachments/

    Create a new attachment. --- Adds a new attachment to the specified record. The actual attachment file must be sent within the request body. Incoming data must be encoded as multipart/form-data.

  • Write

    /v1.2/cashreceipts/{parentpk}/attachments/{id}/

    Partially update an attachment. --- You may change the attachment title, but you cannot replace the actual file.

  • Write

    /v1.2/cashreceipts/{parentpk}/notes/

    Create a new private note. ---

  • Destructive

    /v1.2/cashreceipts/{id}/

    Update a payment received. --- When updating invoice payments or supplier credit payments, you will not be able to change the associated contact or the currency code. In addition, the transaction type cannot be modified.

  • Destructive

    /v1.2/cashreceipts/{id}/

    Delete a payment received. --- Deleting an invoice payment may result in changing the invoice's status. For example, if the invoice was marked as 'paid' it will now revert to 'issued' or 'partially paid'.

  • Destructive

    /v1.2/cashreceipts/{parentpk}/attachments/{id}/

    Delete an attachment. ---

  • Destructive

    /v1.2/cashreceipts/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/cashreceipts/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

Contacts

  • Read

    /v1.2/contacts/

    Get the list of contacts --- All related addresses, phone numbers and email addresses are included in the response.

  • Read

    /v1.2/contacts/{id}/

    Get the details of a single contact. --- Returns all available information for a specific contact.

  • Read

    /v1.2/contacts/{parentpk}/attachments/

    Get the list of attachments. --- The list of attachments for the specified record.

  • Read

    /v1.2/contacts/{parentpk}/attachments/{id}/

    Get a single attachment. ---

  • Read

    /v1.2/contacts/{parentpk}/attachments/{id}/file/

    Get the actual attachment file. --- This endpoint may return a 307 redirect response. To retrieve the file you should follow the redirection.

  • Read

    /v1.2/contacts/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Write

    /v1.2/contacts/

    Create a new contact. --- This endpoint will add a new contact to the specified organization. Although firstname, lastname and company are not required fields, at least one of them must be specified for the record to be valid. The created contact's ID is included in the response.

  • Write

    /v1.2/contacts/{parentpk}/attachments/

    Create a new attachment. --- Adds a new attachment to the specified record. The actual attachment file must be sent within the request body. Incoming data must be encoded as multipart/form-data.

  • Write

    /v1.2/contacts/{parentpk}/attachments/{id}/

    Partially update an attachment. --- You may change the attachment title, but you cannot replace the actual file.

  • Write

    /v1.2/contacts/{parentpk}/notes/

    Create a new private note. ---

  • Destructive

    /v1.2/contacts/{id}/

    Update a contact. --- You must provide at least the required fields for the record to be successfully updated. Any missing parameter will result in preserving the old value.

  • Destructive

    /v1.2/contacts/{id}/

    Delete a contact. --- Note that you cannot delete contacts having relations with other objects (such as invoices, payments etc). Trying to delete such records will result in a 400 HTTP status -with appropriate error messages-.

  • Destructive

    /v1.2/contacts/{parentpk}/attachments/{id}/

    Delete an attachment. ---

  • Destructive

    /v1.2/contacts/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/contacts/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

Creditnotes

  • Read

    /v1.2/creditnotes/

    Get the list of credit notes. --- The response does not include all the credit note details. To retrieve more information about a specific credit note, use the single credit note endpoint.

  • Read

    /v1.2/creditnotes/{id}/

    Get a single credit note. --- Returns all available information for a specific credit note.

  • Read

    /v1.2/creditnotes/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Read

    /v1.2/creditnotes/{id}/pdf/

    Get the document as PDF. --- Download the document in PDF file format.

  • Read

    /v1.2/creditnotes/{parentpk}/applied-credit/

    Get the applied credit. --- The list of credit applied to invoices.

  • Read

    /v1.2/creditnotes/{parentpk}/attachments/

    Get the list of attachments. --- The list of attachments for the specified record.

  • Read

    /v1.2/creditnotes/{parentpk}/attachments/{id}/

    Get a single attachment. ---

  • Read

    /v1.2/creditnotes/{parentpk}/attachments/{id}/file/

    Get the actual attachment file. --- This endpoint may return a 307 redirect response. To retrieve the file you should follow the redirection.

  • Read

    /v1.2/creditnotes/{parentpk}/discussions/

    Get the client discussion. --- A discussion is a series of messages exchanged with the client through the client portal.

  • Read

    /v1.2/creditnotes/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Read

    /v1.2/creditnotes/{parentpk}/sent-email-messages/

    Get the list of tracked email messages for this document. --- Messages are ordered by most recent first.

  • Write

    /v1.2/creditnotes/

    Create a new credit note. --- To create a new credit note, you must first specify the client. You may choose to omit all client-related fields except from the client ID. In this case, the fields will be initialized with values originating from the client's contact record.

  • Write

    /v1.2/creditnotes/{id}/

    Partially update a credit note. --- Use this action to update the credit note tracking, or change it's draft status. Since this method does not modify the credit note items and amounts you can always use it regardless the creditnote status.

  • Write

    /v1.2/creditnotes/{id}/email-from-template/

    The subject and message are rendered from the template resolved via templateid, or the organization's default template if not provided.

  • Write

    /v1.2/creditnotes/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Write

    /v1.2/creditnotes/{parentpk}/applied-credit/

    Bulk apply credit. --- Apply all or part of the remaining credit to a list of invoices. The credit note's client and currency code must match the invoice's corresponding values.

  • Write

    /v1.2/creditnotes/{parentpk}/attachments/

    Create a new attachment. --- Adds a new attachment to the specified record. The actual attachment file must be sent within the request body. Incoming data must be encoded as multipart/form-data.

  • Write

    /v1.2/creditnotes/{parentpk}/attachments/{id}/

    Partially update an attachment. --- You may change the attachment title, but you cannot replace the actual file.

  • Write

    /v1.2/creditnotes/{parentpk}/discussions/

    Create a new discussion message. --- Send a message to the client.

  • Write

    /v1.2/creditnotes/{parentpk}/notes/

    Create a new private note. ---

  • Destructive

    /v1.2/creditnotes/{id}/

    Update a credit note. --- You must send all required fields for the record to be successfully updated. You may only modify draft credit notes. To update issued creditnotes, you should first mark them as draft via the partial update endpoint.

  • Destructive

    /v1.2/creditnotes/{id}/

    Delete a credit note. --- Note that you cannot delete credit notes marked as issued (i.e. the draft field is set to false).

  • Destructive

    /v1.2/creditnotes/{id}/void/

    Mark the document as void or convert it from "void" back to "issued". Notice that when you mark a document as void: It must already be issued. It remains in the system for future reference, but is not involved in Elorus reports.

  • Destructive

    /v1.2/creditnotes/{parentpk}/applied-credit/{id}/

    Delete applied credit. --- Deleting applied credit will just detach the credit from the related invoice. The endpoint's record ID does not refer to the invoice ID, rather than the credit record's ID, returned by the list action.

  • Destructive

    /v1.2/creditnotes/{parentpk}/attachments/{id}/

    Delete an attachment. ---

  • Destructive

    /v1.2/creditnotes/{parentpk}/discussions/{id}/

    Update a discussion message. --- A discussion message can only be updated by its creator.

  • Destructive

    /v1.2/creditnotes/{parentpk}/discussions/{id}/

    Delete a discussion message. --- A discussion message can only be deleted by its creator or an administrator.

  • Destructive

    /v1.2/creditnotes/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/creditnotes/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

Deliverynotes

  • Read

    /v1.2/deliverynotes/

    Get the list of delivery notes. --- The response does not include all the delivery note details. To retrieve more information about a specific delivery note, use the single delivery note endpoint.

  • Read

    /v1.2/deliverynotes/{id}/

    Get a single delivery note. --- Returns all available information for a specific delivery note.

  • Read

    /v1.2/deliverynotes/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Read

    /v1.2/deliverynotes/{id}/pdf/

    Get the document as PDF. --- Download the document in PDF file format.

  • Read

    /v1.2/deliverynotes/{parentpk}/attachments/

    Get the list of attachments. --- The list of attachments for the specified record.

  • Read

    /v1.2/deliverynotes/{parentpk}/attachments/{id}/

    Get a single attachment. ---

  • Read

    /v1.2/deliverynotes/{parentpk}/attachments/{id}/file/

    Get the actual attachment file. --- This endpoint may return a 307 redirect response. To retrieve the file you should follow the redirection.

  • Read

    /v1.2/deliverynotes/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Read

    /v1.2/deliverynotes/{parentpk}/sent-email-messages/

    Get the list of tracked email messages for this document. --- Messages are ordered by most recent first.

  • Write

    /v1.2/deliverynotes/

    Create a new delivery note. --- To create a new delivery note, you must first specify the contact. You may choose to omit all contact-related fields except from the contact ID. In this case, the fields will be initialized with values originating from the contact record.

  • Write

    /v1.2/deliverynotes/{id}/

    Partially update a delivery note. --- Use this action to update the delivery note template, or change it's draft status. Since this method does not modify the delivery note items and amounts you can always use it regardless the delivery note status.

  • Write

    /v1.2/deliverynotes/{id}/email-from-template/

    The subject and message are rendered from the template resolved via templateid, or the organization's default template if not provided.

  • Write

    /v1.2/deliverynotes/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Write

    /v1.2/deliverynotes/{parentpk}/attachments/

    Create a new attachment. --- Adds a new attachment to the specified record. The actual attachment file must be sent within the request body. Incoming data must be encoded as multipart/form-data.

  • Write

    /v1.2/deliverynotes/{parentpk}/attachments/{id}/

    Partially update an attachment. --- You may change the attachment title, but you cannot replace the actual file.

  • Write

    /v1.2/deliverynotes/{parentpk}/notes/

    Create a new private note. ---

  • Destructive

    /v1.2/deliverynotes/{id}/

    Update a delivery note. --- You must send all required fields for the record to be successfully updated. You may only modify draft delivery notes. To update issued delivery notes, you should first mark them as draft via the partial update endpoint.

  • Destructive

    /v1.2/deliverynotes/{id}/

    Delete a delivery note. --- Note that you cannot delete delivery notes marked as issued (i.e. the draft field is set to false).

  • Destructive

    /v1.2/deliverynotes/{id}/void/

    Mark the document as void or convert it from "void" back to "issued". Notice that when you mark a document as void: It must already be issued. It remains in the system for future reference, but is not involved in Elorus reports.

  • Destructive

    /v1.2/deliverynotes/{parentpk}/attachments/{id}/

    Delete an attachment. ---

  • Destructive

    /v1.2/deliverynotes/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/deliverynotes/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

Documenttypes

  • Read

    /v1.2/documenttypes/

    Get the list of document types. ---

  • Read

    /v1.2/documenttypes/{id}/

    Get a single document type. ---

  • Read

    /v1.2/documenttypes/{parentpk}/sequences/

    Get the numbering sequences of a document type. ---

  • Write

    /v1.2/documenttypes/{parentpk}/sequences/

    Create a numbering sequence. ---

  • Destructive

    /v1.2/documenttypes/{parentpk}/sequences/delete/

    Delete a numbering sequence. ---

  • Destructive

    /v1.2/documenttypes/{parentpk}/sequences/rename/

    Rename a numbering sequence. ---

Emailtemplates

  • Read

    /v1.2/emailtemplates/

    Get the list of email templates. ---

  • Read

    /v1.2/emailtemplates/{id}/

    Get a single email template. ---

  • Write

    /v1.2/emailtemplates/

    Create an email template. ---

  • Destructive

    /v1.2/emailtemplates/{id}/

    Update an email template. ---

  • Destructive

    /v1.2/emailtemplates/{id}/

    Destroy an email template. ---

Estimates

  • Read

    /v1.2/estimates/

    Get the list of estimates. --- The response does not include all the estimate details. To retrieve more information about a specific estimate, use the single estimate endpoint.

  • Read

    /v1.2/estimates/{id}/

    Get a single estimate. --- Returns all available information for a specific estimate.

  • Read

    /v1.2/estimates/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Read

    /v1.2/estimates/{id}/pdf/

    Get the document as PDF. --- Download the document in PDF file format.

  • Read

    /v1.2/estimates/{parentpk}/attachments/

    Get the list of attachments. --- The list of attachments for the specified record.

  • Read

    /v1.2/estimates/{parentpk}/attachments/{id}/

    Get a single attachment. ---

  • Read

    /v1.2/estimates/{parentpk}/attachments/{id}/file/

    Get the actual attachment file. --- This endpoint may return a 307 redirect response. To retrieve the file you should follow the redirection.

  • Read

    /v1.2/estimates/{parentpk}/discussions/

    Get the client discussion. --- A discussion is a series of messages exchanged with the client through the client portal.

  • Read

    /v1.2/estimates/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Read

    /v1.2/estimates/{parentpk}/sent-email-messages/

    Get the list of tracked email messages for this document. --- Messages are ordered by most recent first.

  • Write

    /v1.2/estimates/

    Create a new estimate. --- To create a new estimate, you must first specify the client. You may choose to omit all client-related fields except from the client ID. In this case, the fields will be initialized with values originating from the client's contact record.

  • Write

    /v1.2/estimates/{id}/

    Partially update an estimate. --- Use this action to update the estimate template, or change it's draft status. Since this method does not modify the estimate items and amounts you can always use it regardless the estimate status.

  • Write

    /v1.2/estimates/{id}/email-from-template/

    The subject and message are rendered from the template resolved via templateid, or the organization's default template if not provided.

  • Write

    /v1.2/estimates/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Write

    /v1.2/estimates/{parentpk}/attachments/

    Create a new attachment. --- Adds a new attachment to the specified record. The actual attachment file must be sent within the request body. Incoming data must be encoded as multipart/form-data.

  • Write

    /v1.2/estimates/{parentpk}/attachments/{id}/

    Partially update an attachment. --- You may change the attachment title, but you cannot replace the actual file.

  • Write

    /v1.2/estimates/{parentpk}/discussions/

    Create a new discussion message. --- Send a message to the client.

  • Write

    /v1.2/estimates/{parentpk}/notes/

    Create a new private note. ---

  • Destructive

    /v1.2/estimates/{id}/

    Update an estimate. --- You must send all required fields for the record to be successfully updated. You may only modify draft estimates. To update issued estimates, you should first mark them as draft via the partial update endpoint.

  • Destructive

    /v1.2/estimates/{id}/

    Delete an estimate. --- Note that you cannot delete estimates marked as issued (i.e. the draft field is set to false).

  • Destructive

    /v1.2/estimates/{parentpk}/attachments/{id}/

    Delete an attachment. ---

  • Destructive

    /v1.2/estimates/{parentpk}/discussions/{id}/

    Update a discussion message. --- A discussion message can only be updated by its creator.

  • Destructive

    /v1.2/estimates/{parentpk}/discussions/{id}/

    Delete a discussion message. --- A discussion message can only be deleted by its creator or an administrator.

  • Destructive

    /v1.2/estimates/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/estimates/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

Expensecategories

  • Read

    /v1.2/expensecategories/

    Get the list of expense categories. ---

  • Read

    /v1.2/expensecategories/{id}/

    Get a single expense category. ---

Expenses

  • Read

    /v1.2/expenses/

    Get the list of expenses. --- The response does not include all the expense details. To retrieve more information about a specific expense, use the single expense endpoint.

  • Read

    /v1.2/expenses/{id}/

    Get a single expense. --- Returns all available information for a specific expense.

  • Read

    /v1.2/expenses/{parentpk}/attachments/

    Get the list of attachments. --- The list of attachments for the specified record.

  • Read

    /v1.2/expenses/{parentpk}/attachments/{id}/

    Get a single attachment. ---

  • Read

    /v1.2/expenses/{parentpk}/attachments/{id}/file/

    Get the actual attachment file. --- This endpoint may return a 307 redirect response. To retrieve the file you should follow the redirection.

  • Read

    /v1.2/expenses/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Write

    /v1.2/expenses/

    Create a new expense. --- Expense lines & amounts The expense's net and total amount will be calculated automatically and their values will depend on the calculator mode and the line items.

  • Write

    /v1.2/expenses/{parentpk}/attachments/

    Create a new attachment. --- Adds a new attachment to the specified record. The actual attachment file must be sent within the request body. Incoming data must be encoded as multipart/form-data.

  • Write

    /v1.2/expenses/{parentpk}/attachments/{id}/

    Partially update an attachment. --- You may change the attachment title, but you cannot replace the actual file.

  • Write

    /v1.2/expenses/{parentpk}/notes/

    Create a new private note. ---

  • Destructive

    /v1.2/expenses/{id}/

    To update the line items, the endpoint expects that you send a complete list of the new items. For existing lines you must send over their IDs (as returned by the retrieve endpoint) along with any possible changes.

  • Destructive

    /v1.2/expenses/{id}/

    Delete an expense. ---

  • Destructive

    /v1.2/expenses/{parentpk}/attachments/{id}/

    Delete an attachment. ---

  • Destructive

    /v1.2/expenses/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/expenses/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

Goodsreceipts

  • Read

    /v1.2/goodsreceipts/

    GET /v1.2/goodsreceipts/

  • Read

    /v1.2/goodsreceipts/{id}/

    Get a single goods receipt. --- Returns all available information for a specific goods receipt.

  • Read

    /v1.2/goodsreceipts/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Read

    /v1.2/goodsreceipts/{id}/pdf/

    Get the document as PDF. --- Download the document in PDF file format.

  • Read

    /v1.2/goodsreceipts/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Read

    /v1.2/goodsreceipts/{parentpk}/sent-email-messages/

    Get the list of tracked email messages for this document. --- Messages are ordered by most recent first.

  • Write

    /v1.2/goodsreceipts/

    Create a new goods receipt. --- To create a new goods receipt, you must first specify the supplier. You may choose to omit all supplier-related fields except from the supplier ID. In this case, the fields will be initialized with values originating from the supplier record.

  • Write

    /v1.2/goodsreceipts/{id}/

    Partially update a goods receipt. --- Use this action to update the goods receipt template, or change its draft status. Since this method does not modify the goods receipt items you can always use it regardless the goods receipt status.

  • Write

    /v1.2/goodsreceipts/{id}/email-from-template/

    The subject and message are rendered from the template resolved via templateid, or the organization's default template if not provided.

  • Write

    /v1.2/goodsreceipts/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Write

    /v1.2/goodsreceipts/{parentpk}/notes/

    Create a new private note. ---

  • Destructive

    /v1.2/goodsreceipts/{id}/

    Update a goods receipt. --- You must send all required fields for the record to be successfully updated. You may only modify draft goods receipts. To update issued goods receipts, you should first mark them as draft via the partial update endpoint.

  • Destructive

    /v1.2/goodsreceipts/{id}/

    Delete a goods receipt. --- Note that you cannot delete goods receipts marked as issued (i.e. the draft field is set to false).

  • Destructive

    /v1.2/goodsreceipts/{id}/void/

    Mark the document as void or convert it from "void" back to "issued". Notice that when you mark a document as void: It must already be issued. It remains in the system for future reference, but is not involved in Elorus reports.

  • Destructive

    /v1.2/goodsreceipts/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/goodsreceipts/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

Goodsreceiptsequences

  • Read

    /v1.2/goodsreceiptsequences/

    Get the list of goods receipt sequences. ---

  • Write

    /v1.2/goodsreceiptsequences/

    Create a goods receipt sequence. ---

  • Destructive

    /v1.2/goodsreceiptsequences/delete/

    Delete a numbering sequence. ---

  • Destructive

    /v1.2/goodsreceiptsequences/rename/

    Rename a numbering sequence. ---

Invoices

  • Read

    /v1.2/invoices/

    Get the list of invoices. --- The response does not include all the invoice details. To retrieve more information about a specific invoice, use the single invoice endpoint.

  • Read

    /v1.2/invoices/{id}/

    Get a single invoice. --- Returns all available information for a specific invoice.

  • Read

    /v1.2/invoices/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Read

    /v1.2/invoices/{id}/pdf/

    Get the document as PDF. --- Download the document in PDF file format.

  • Read

    /v1.2/invoices/{parentpk}/applied-credit/

    Get the applied credit. --- The list of credit applied to invoices.

  • Read

    /v1.2/invoices/{parentpk}/attachments/

    Get the list of attachments. --- The list of attachments for the specified record.

  • Read

    /v1.2/invoices/{parentpk}/attachments/{id}/

    Get a single attachment. ---

  • Read

    /v1.2/invoices/{parentpk}/attachments/{id}/file/

    Get the actual attachment file. --- This endpoint may return a 307 redirect response. To retrieve the file you should follow the redirection.

  • Read

    /v1.2/invoices/{parentpk}/discussions/

    Get the client discussion. --- A discussion is a series of messages exchanged with the client through the client portal.

  • Read

    /v1.2/invoices/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Read

    /v1.2/invoices/{parentpk}/sent-email-messages/

    Get the list of tracked email messages for this document. --- Messages are ordered by most recent first.

  • Write

    /v1.2/invoices/

    Create a new invoice. --- To create a new invoice, you must first specify the client. You may choose to omit all client-related fields except from the client ID. In this case, the fields will be initialized with values originating from the client's contact record.

  • Write

    /v1.2/invoices/{id}/

    Partially update an invoice. --- Use this action to update the invoice payment gateways, tracking, or change it's draft status. Since this method does not modify the invoice items and amounts you can always use it regardless the invoice status.

  • Write

    /v1.2/invoices/{id}/email-from-template/

    The subject and message are rendered from the template resolved via templateid, or the organization's default template if not provided.

  • Write

    /v1.2/invoices/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Write

    /v1.2/invoices/{parentpk}/applied-credit/

    Bulk apply credit. --- Apply all or part of the remaining credit to a list of invoices. The credit note's client and currency code must match the invoice's corresponding values.

  • Write

    /v1.2/invoices/{parentpk}/attachments/

    Create a new attachment. --- Adds a new attachment to the specified record. The actual attachment file must be sent within the request body. Incoming data must be encoded as multipart/form-data.

  • Write

    /v1.2/invoices/{parentpk}/attachments/{id}/

    Partially update an attachment. --- You may change the attachment title, but you cannot replace the actual file.

  • Write

    /v1.2/invoices/{parentpk}/discussions/

    Create a new discussion message. --- Send a message to the client.

  • Write

    /v1.2/invoices/{parentpk}/notes/

    Create a new private note. ---

  • Destructive

    /v1.2/invoices/{id}/

    Update an invoice. --- You must send all required fields for the record to be successfully updated. You may only modify draft invoices. To update issued invoices, you should first mark them as draft via the partial update endpoint.

  • Destructive

    /v1.2/invoices/{id}/

    Delete an invoice. --- Note that you cannot delete invoices marked as issued (i.e. the draft field is set to false).

  • Destructive

    /v1.2/invoices/{id}/void/

    Mark the document as void or convert it from "void" back to "issued". Notice that when you mark a document as void: It must already be issued. It remains in the system for future reference, but is not involved in Elorus reports.

  • Destructive

    /v1.2/invoices/{parentpk}/applied-credit/{id}/

    Delete applied credit. --- Deleting applied credit will just detach the credit from the related invoice. The endpoint's record ID does not refer to the invoice ID, rather than the credit record's ID, returned by the list action.

  • Destructive

    /v1.2/invoices/{parentpk}/attachments/{id}/

    Delete an attachment. ---

  • Destructive

    /v1.2/invoices/{parentpk}/discussions/{id}/

    Update a discussion message. --- A discussion message can only be updated by its creator.

  • Destructive

    /v1.2/invoices/{parentpk}/discussions/{id}/

    Delete a discussion message. --- A discussion message can only be deleted by its creator or an administrator.

  • Destructive

    /v1.2/invoices/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/invoices/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

Organizationbranch

  • Read

    /v1.2/organizationbranch/

    Get the list of organization branches. ---

  • Read

    /v1.2/organizationbranch/{id}/

    Get a single organization branch. ---

  • Write

    /v1.2/organizationbranch/

    Create an organization branch. ---

  • Write

    /v1.2/organizationbranch/{id}/

    Partially update an organization branch. ---

  • Destructive

    /v1.2/organizationbranch/{id}/

    Update an organization branch. ---

  • Destructive

    /v1.2/organizationbranch/{id}/

    Delete an organization branch. ---

Paymentgateways

  • Read

    /v1.2/paymentgateways/

    Get the list of payment gateways. ---

Products

  • Read

    /v1.2/products/

    Get the list of products / services. --- The response does not include all the products / services details. To retrieve more information about a specific product / service, use the single products / services endpoint.

  • Read

    /v1.2/products/{id}/

    Get a single product / service. --- Returns all available information for a specific product / service.

  • Read

    /v1.2/products/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Read

    /v1.2/products/{parentpk}/stockadjustments/

    Get the list of manual stock adjustments for the product / service.

  • Read

    /v1.2/products/{parentpk}/stockadjustments/{id}/

    Get a single manual stock adjustment.

  • Write

    /v1.2/products/

    Create a new product / service. ---

  • Write

    /v1.2/products/{parentpk}/notes/

    Create a new private note. ---

  • Write

    /v1.2/products/{parentpk}/stockadjustments/

    Create a new stock adjustment. --- Modify the product's stock without issuing invoices or bills.

  • Destructive

    /v1.2/products/{id}/

    Update a product / service. --- You must provide at least all the required fields for the record to be successfully updated. Omit any optional parameter to keep the old value.

  • Destructive

    /v1.2/products/{id}/

    Delete a product / service. --- If you delete a product that is associated with an invoice line, the invoice will be decoupled from the product. Other than that, the invoice line will be left intact and the product will be successfully deleted.

  • Destructive

    /v1.2/products/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/products/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

  • Destructive

    /v1.2/products/{parentpk}/stockadjustments/{id}/

    Delete an existing stock adjustment.

Projects

  • Read

    /v1.2/projects/

    Get the list of projects. ---

  • Read

    /v1.2/projects/{id}/

    Get a single project. ---

  • Read

    /v1.2/projects/{parentpk}/attachments/

    Get the list of attachments. --- The list of attachments for the specified record.

  • Read

    /v1.2/projects/{parentpk}/attachments/{id}/

    Get a single attachment. ---

  • Read

    /v1.2/projects/{parentpk}/attachments/{id}/file/

    Get the actual attachment file. --- This endpoint may return a 307 redirect response. To retrieve the file you should follow the redirection.

  • Read

    /v1.2/projects/{parentpk}/discussions/

    Get the client discussion. --- A discussion is a series of messages exchanged with the client through the client portal.

  • Read

    /v1.2/projects/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Read

    /v1.2/projects/{parentpk}/projectextrafees/

    Get the list of project extra fees. ---

  • Read

    /v1.2/projects/{parentpk}/projectextrafees/{id}/

    Get a single project extra fee. ---

  • Write

    /v1.2/projects/

    Create a new project. --- Along with a project, you can specify the project members (users that can track time for the project), as well as project-specific tasks.

  • Write

    /v1.2/projects/{parentpk}/attachments/

    Create a new attachment. --- Adds a new attachment to the specified record. The actual attachment file must be sent within the request body. Incoming data must be encoded as multipart/form-data.

  • Write

    /v1.2/projects/{parentpk}/attachments/{id}/

    Partially update an attachment. --- You may change the attachment title, but you cannot replace the actual file.

  • Write

    /v1.2/projects/{parentpk}/discussions/

    Create a new discussion message. --- Send a message to the client.

  • Write

    /v1.2/projects/{parentpk}/notes/

    Create a new private note. ---

  • Write

    /v1.2/projects/{parentpk}/projectextrafees/

    Create a new project extra fee. ---

  • Write

    /v1.2/projects/{parentpk}/projectextrafees/{id}/

    Partially update a project extra fee. ---

  • Destructive

    /v1.2/projects/{id}/

    Update an existing project. ---

  • Destructive

    /v1.2/projects/{id}/

    Delete a project. ---

  • Destructive

    /v1.2/projects/{parentpk}/attachments/{id}/

    Delete an attachment. ---

  • Destructive

    /v1.2/projects/{parentpk}/discussions/{id}/

    Update a discussion message. --- A discussion message can only be updated by its creator.

  • Destructive

    /v1.2/projects/{parentpk}/discussions/{id}/

    Delete a discussion message. --- A discussion message can only be deleted by its creator or an administrator.

  • Destructive

    /v1.2/projects/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/projects/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

  • Destructive

    /v1.2/projects/{parentpk}/projectextrafees/{id}/

    Update a project extra fee. ---

  • Destructive

    /v1.2/projects/{parentpk}/projectextrafees/{id}/

    Delete a project extra fee. ---

Recurringinvoices

  • Read

    /v1.2/recurringinvoices/

    Get the list of recurring invoices. --- The response does not include all the recurring invoice details. To retrieve more information about a specific recurring invoice, use the single recurring invoice endpoint.

  • Read

    /v1.2/recurringinvoices/{id}/

    Get a single recurring invoice. --- Returns all available information for a specific recurring invoice.

  • Read

    /v1.2/recurringinvoices/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Write

    /v1.2/recurringinvoices/

    Create a new recurring invoice. --- You must specify the recurring schedule as well as the details of the generated invoices. As far as the schedule is concerned, you may leave the enddatetime field blank to run the recurring procedure forever.

  • Write

    /v1.2/recurringinvoices/{parentpk}/notes/

    Create a new private note. ---

  • Destructive

    /v1.2/recurringinvoices/{id}/

    When changing the invoice client, all client fields will be updated based on the new contact record, unless you explicitly specify their values. To update the line items, the endpoint expects that you send a complete list of the new items.

  • Destructive

    /v1.2/recurringinvoices/{id}/

    Delete a recurring invoice. --- Does not delete any documents, just the schedule that creates them.

  • Destructive

    /v1.2/recurringinvoices/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/recurringinvoices/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

Suppliercredits

  • Read

    /v1.2/suppliercredits/

    Get the list of supplier credits. --- The response does not include all the supplier credit details. To retrieve more information about a specific record, use the single supplier credit endpoint.

  • Read

    /v1.2/suppliercredits/{id}/

    Get a single supplier credit. --- Returns all available information for a specific supplier credit.

  • Read

    /v1.2/suppliercredits/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Read

    /v1.2/suppliercredits/{id}/pdf/

    Get the document as PDF. --- Only self-billed invoices will be printed out to PDF.

  • Read

    /v1.2/suppliercredits/{parentpk}/applied-credit/

    Get the applied credit. --- The list of credit applied to bills.

  • Read

    /v1.2/suppliercredits/{parentpk}/attachments/

    Get the list of attachments. --- The list of attachments for the specified record.

  • Read

    /v1.2/suppliercredits/{parentpk}/attachments/{id}/

    Get a single attachment. ---

  • Read

    /v1.2/suppliercredits/{parentpk}/attachments/{id}/file/

    Get the actual attachment file. --- This endpoint may return a 307 redirect response. To retrieve the file you should follow the redirection.

  • Read

    /v1.2/suppliercredits/{parentpk}/notes/

    Get the list of private notes. --- These notes are internal and can only be accessed by your team.

  • Read

    /v1.2/suppliercredits/{parentpk}/sent-email-messages/

    Get the list of tracked email messages for this document. --- Messages are ordered by most recent first.

  • Write

    /v1.2/suppliercredits/

    Create a new supplier credit. ---

  • Write

    /v1.2/suppliercredits/{id}/

    Partially update a supplier credit. Note that you cannot delete supplier credits marked as issued (i.e. the draft field is set to false). --- You may modify even issued supplier credits.

  • Write

    /v1.2/suppliercredits/{id}/email-from-template/

    The subject and message are rendered from the template resolved via templateid, or the organization's default template if not provided.

  • Write

    /v1.2/suppliercredits/{id}/email/

    Send the document by email. --- You may retrieve the default email subject, message, etc. with a GET request. Use POST to submit the email. In most cases you want to send the data exactly as returned by the GET action. The POST response contains the tracked email message.

  • Write

    /v1.2/suppliercredits/{parentpk}/applied-credit/

    Bulk apply credit. --- Apply all or part of the remaining credit to a list of bills. The supplier credit's supplier and currency code must match the bill's corresponding values.

  • Write

    /v1.2/suppliercredits/{parentpk}/attachments/

    Create a new attachment. --- Adds a new attachment to the specified record. The actual attachment file must be sent within the request body. Incoming data must be encoded as multipart/form-data.

  • Write

    /v1.2/suppliercredits/{parentpk}/attachments/{id}/

    Partially update an attachment. --- You may change the attachment title, but you cannot replace the actual file.

  • Write

    /v1.2/suppliercredits/{parentpk}/notes/

    Create a new private note. ---

  • Destructive

    /v1.2/suppliercredits/{id}/

    Update a supplier credit. --- You must send all required fields for the record to be successfully updated. You may only modify draft supplier credits.

  • Destructive

    /v1.2/suppliercredits/{id}/

    Delete a supplier credit. --- Note that you cannot delete supplier credits marked as issued (i.e. the draft field is set to false).

  • Destructive

    /v1.2/suppliercredits/{id}/void/

    Mark the document as void or convert it from "void" back to "issued". Notice that when you mark a document as void: It must already be issued. It remains in the system for future reference, but is not involved in Elorus reports.

  • Destructive

    /v1.2/suppliercredits/{parentpk}/applied-credit/{id}/

    Delete applied credit. --- Deleting applied credit will just detach the credit from the related bill. The endpoint's record ID does not refer to the bill ID, rather than the credit record's ID, returned by the list action.

  • Destructive

    /v1.2/suppliercredits/{parentpk}/attachments/{id}/

    Delete an attachment. ---

  • Destructive

    /v1.2/suppliercredits/{parentpk}/notes/{id}/

    Update a private note. --- A note can only be updated by its creator

  • Destructive

    /v1.2/suppliercredits/{parentpk}/notes/{id}/

    Delete a private note. --- A note can only be updated by its creator or an administrator.

Tasks

  • Read

    /v1.2/tasks/

    Get the list of tasks. ---

  • Read

    /v1.2/tasks/{id}/

    Get a single task. ---

  • Write

    /v1.2/tasks/

    Create a new task. --- Leave the project field empty to create a global task, or specify a project to restrict time tracking to that specific project.

  • Destructive

    /v1.2/tasks/{id}/

    Update an existing task. ---

  • Destructive

    /v1.2/tasks/{id}/

    Delete a task. ---

Taxes

  • Read

    /v1.2/taxes/

    Get the list of taxes. ---

  • Read

    /v1.2/taxes/{id}/

    Get a single tax. ---

Templates

  • Read

    /v1.2/templates/

    Get the list of templates. ---

  • Read

    /v1.2/templates/{id}/

    Get a single template. ---

Timeentries

  • Read

    /v1.2/timeentries/

    Get the list of time entries.

  • Read

    /v1.2/timeentries/{id}/

    Retrieve an existing time entry.

  • Write

    /v1.2/timeentries/

    Create a new time entry.

  • Destructive

    /v1.2/timeentries/{id}/

    Update an existing time entry.

  • Destructive

    /v1.2/timeentries/{id}/

    Delete an existing time entry.

  • Destructive

    /v1.2/timeentries/{id}/mark-billed/

    Set a billed time entry as forcibly billed. Ignore already billed time entries.

  • Destructive

    /v1.2/timeentries/{id}/mark-unbilled/

    Set a billed time entry as unbilled. Ignore already unbilled time entries.

Trackingcategories

  • Read

    /v1.2/trackingcategories/

    Get the list of tracking categories. ---

  • Read

    /v1.2/trackingcategories/{id}/

    Get a single tracking category. ---

Unitofmeasurement

  • Read

    /v1.2/unitofmeasurement/

    Get list of units of measurement.

  • Read

    /v1.2/unitofmeasurement/{id}/

    Get a single unit of measurement.

  • Write

    /v1.2/unitofmeasurement/

    Create a new unit of measurement.

  • Write

    /v1.2/unitofmeasurement/{id}/

    Partially update an existing unit of measurement.

  • Destructive

    /v1.2/unitofmeasurement/{id}/

    Update an existing unit of measurement.

  • Destructive

    /v1.2/unitofmeasurement/{id}/

    Delete an existing unit of measurement.

Users

  • Read

    /v1.2/users/

    Get the list of organization users. --- This endpoint is designed to facilitate interaction with other sections of the API, such as projects, where project members are identified by their corresponding user ID.

Userteams

  • Read

    /v1.2/userteams/

    Get the list of user teams. ---

Warehouse

  • Read

    /v1.2/warehouse/

    Get the list of warehouses. ---

  • Read

    /v1.2/warehouse/{id}/

    Get a single warehouse. ---

  • Write

    /v1.2/warehouse/

    Create a warehouse. ---

  • Write

    /v1.2/warehouse/{id}/

    Partially update a warehouse. ---

  • Destructive

    /v1.2/warehouse/{id}/

    Update a warehouse. ---

  • Destructive

    /v1.2/warehouse/{id}/

    Delete a warehouse. ---

See How connections work for access and permissions, or browse all integrations.

Reference date: October 27, 2026. Elorus API docs.