ForceManager

Delete Account Address via DELETE /accountAddresses/{account_address_id}. This endpoint allows you to delete a specific Account Address from the user's ForceManager implementation database. If the specified Account Address does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Account via DELETE /accounts/{account_id}. This endpoint allows you to delete a specific Account from the user's ForceManager implementation database. If the specified Account does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Account Segment via DELETE /accountSegments/{account_segment_id}. This endpoint allows you to delete a specific Account Segment from the user's ForceManager implementation database. If the specified Account Segment does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Related Account via DELETE /accountsRelated/{related_account_id}. This endpoint allows you to delete a specific Related Account from the user's ForceManager implementation database. If the specified Related Account does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Related Account Type via DELETE /accountsRelations/{related_account_type_id}. This endpoint allows you to delete a specific Related Account Type from the user's ForceManager implementation database. If the specified Related Account Type does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Account Status via DELETE /accountStatuses/{account_status_id}. This endpoint allows you to delete a specific Account Status from the user's ForceManager implementation database. If the specified Account Status does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Activity via DELETE /activities/{activity_id}. This endpoint allows you to delete a specific Activity from the user's ForceManager implementation database. If the specified Activity does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Activity Type via DELETE /activityTypes/{activity_type_id}. This endpoint allows you to delete a specific Activity Type from the user's ForceManager implementation database. If the specified Activity Type does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Branch via DELETE /branches/{branch_id}. This endpoint allows you to delete a specific Branch from the Value List. If the specified Branch does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Calendar via DELETE /calendar/{calendar_entry_id}. This endpoint allows you to delete a specific calendar Event or Task from the user's ForceManager implementation database. If the specified calendar Event or Task does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Call via DELETE /calls/{call_id}. This endpoint allows you to delete a specific Call from the user's ForceManager implementation database. If the specified Call does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Campaign Question via DELETE /campaignQuestions/{question_id}. This endpoint allows you to delete a specific Campaign Question from the user's ForceManager implementation database. If the specified Campaign Question does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Question Answer via DELETE /campaignQuestions/{question_id}/answers/{answer_id}. This endpoint allows you to delete a specific Campaign Question Answer from the user's ForceManager implementation database. If the specified Campaign Question Answer does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Question Value via DELETE /campaignQuestions/{question_id}/values/{value_id}. This endpoint allows you to delete a specific Campaign Question Value from the user's ForceManager implementation database. If the specified Campaign Question Value does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Campaign via DELETE /campaigns/{campaign_id}. This endpoint allows you to delete a specific Campaign from the user's ForceManager implementation database. If the specified Campaign does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Campaign Account via DELETE /campaigns/{campaign_id}/entities/{entity_id}. This endpoint allows you to delete a specific Campaign Account from the user's ForceManager implementation database. If the specified Campaign Account does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Contact via DELETE /contacts/{contact_id}. This endpoint allows you to delete a specific Contact from the user's ForceManager account database. If the specified Contact does not exist, the response will be a "bad request". This operation cannot be undone. <br>

Delete Contact Type via DELETE /contactTypes/{contact_type_id}. This endpoint allows you to delete a specific Contact Type from the user's ForceManager implementation database. If the specified Contact Type does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Picture via DELETE /documents/{document_id}. This endpoint allows you to delete a specific Picture from the user's ForceManager implementation database. If the specified Picture does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Tabs via DELETE /extrafieldsTabs/{tab_id}. This endpoint allows you to delete a specific Tab from the user's ForceManager implementation database. If the specified Tab does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Webhook via DELETE /hooks/{webhook_id}. This endpoint allows you to delete a specific Webhook from the user's ForceManager implementation database. If the specified Webhook does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Account Type via DELETE /list/accountTypes/{account_type_id}. This endpoint allows you to delete a specific Account Type from the user's ForceManager implementation database. If the specified Account Type does not exist, the response will be a "bad request". This operation cannot be undone.

Delete List via DELETE /list/{list_name}. This endpoint allows you to delete a specific List. If the specified List does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Value via DELETE /list/{list_name}/{value_id}. This endpoint allows you to delete a specific Value from a Value List. If the specified Value does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Opportunity via DELETE /opportunities/{opportunity_id}. This endpoint allows you to delete a specific Opportunity from the user's ForceManager implementation database. If the specified Opportunity does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Opportunity Status via DELETE /opportunityStatuses/{opportunity_status_id}. This endpoint allows you to delete a specific Opportunity Status from the user's ForceManager implementation database. If the specified Opportunity Status does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Opportunity Type via DELETE /opportunityTypes/{opportunity_type_id}. This endpoint allows you to delete a specific Opportunity Type from the user's ForceManager implementation database. If the specified Opportunity Type does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Order Types via DELETE /orderTypes/{order_type_id}. This endpoint allows you to delete a specific Order Types from the user's ForceManager implementation database. If the specified Order Types does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Product Category via DELETE /productCategories/{product_category_id}. This endpoint allows you to delete a specific Product Category. If the specified Product Category does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Product Family via DELETE /productFamilies/{product_family_id}. This endpoint allows you to delete a specific Product Family. If the specified Product Family does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Product Rate via DELETE /productRates/{product_rate_id}. This endpoint allows you to delete a specific Product Rate. If the specified Product Rate does not exist, the response will be a "bad request". This operation cannot be undone.

Bulk Delete Products via DELETE /products/bulk. This endpoint allows you to delete Multiple Products (100 entities for request) from the user's ForceManager implementation database. If the specified Account does not exist, the response will be a "bad request". This operation cannot be undone. Send an ARRAY of `{guid, id}` objects -- authored from the vendor's REQUEST prose, because the contract declares no requestBody here, and unverified against the live API. Cap 100 entities per request; one result row per `guid`.

Delete Product via DELETE /products/{product_id}. This endpoint allows you to delete a specific Product from the user's ForceManager implementation database. If the specified Product does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Rate via DELETE /rates/{rate_id}. This endpoint allows you to delete a specific Rate from the user's ForceManager implementation database. If the specified Rate does not exist, the response will be a "bad request". This operation cannot be undone.

Bulk Delete Resources via DELETE /{resource}/bulk. This endpoint allows you to delete multiple Resources (120 entities for request) from the user's ForceManager implementation database. If the specified Resource does not exist, the response will be a "bad request". This operation cannot be undone. Send an ARRAY of `{guid, id}` objects -- authored from the vendor's REQUEST prose, because the contract declares no requestBody here, and unverified against the live API. Cap 120 entities per request; one result row per `guid`. `resource` is the entity name in the first path segment; the vendor documents Accounts, Contacts, Opportunities, Orders and Value Lists are the examples the vendor gives ('e.g.'), so the list is not exhaustive. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged.

Delete Warning of a Resource via DELETE /{resource}/{resource_id}/warnings/{warning_id}. This endpoint allows you to delete a Warning of a specific Resource (accounts, opportunities, products, salesorders) based on JSON input. `resource` is the entity name in the first path segment; the vendor documents `accounts`, `opportunities`, `products`, `salesorders`. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status. This operation cannot be undone.

Delete Sale via DELETE /sales/{sale_id}. This endpoint allows you to delete a specific Sale from the user's ForceManager implementation database. If the specified Sale does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Order Header via DELETE /salesorders/{order_id}. This endpoint allows you to delete a specific Order Header from the user's ForceManager implementation database. If the specified Order Header does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Order Line via DELETE /salesordersLines/{order_line_id}. This endpoint allows you to delete a specific Order Line from the user's ForceManager implementation database. If the specified Order Line does not exist, the response will be a "bad request". This operation cannot be undone.

Delete Order Status via DELETE /salesorderStatuses/{order_status_id}. This endpoint allows you to delete a specific Order Status from the user's ForceManager implementation database. If the specified Order Status does not exist, the response will be a "bad request". This operation cannot be undone.

Delete User via DELETE /users/{user_id}. This endpoint allows you to delete a specific User from the user's ForceManager account database. If the specified User does not exist, the response will be a "bad request". This operation cannot be undone. <br>

Delete Roles in User via DELETE /users/{user_id}/roles. This endpoint allows you to delete a specific User's Role from the user's ForceManager account database. If the specified User's Role does not exist, the response will be a "bad request". This operation cannot be undone.

Delete User Type via DELETE /userTypes/{user_type_id}. Deletes one User Type by its integer id. If the specified User Type does not exist, the response is a bad request. This operation cannot be undone.

List Account Addresses via GET /accountAddresses. Returns all Account Addresses available in the user's ForceManager implementation database.

Get Account Address via GET /accountAddresses/{account_address_id}. This endpoint retrieves data of a specific Account Address based on JSON input. The API returns a single Address available to the user, according to the unique ID provided. If the specified Account Address does not exist, the response will be a "bad request".

Account Addresses schema via GET /accountAddresses/schema. The Schema is metadata that tells you how the data is structured for this specific Value list.

List Accounts via GET /accounts. Returns all Accounts available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Account via GET /accounts/{account_id}. This endpoint retrieves data of a specific Account based on JSON input. The API returns a single Account available to the user, according to the unique ID provided. If the specified Account does not exist, the response will be a "bad request". `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Accounts schema via GET /accounts/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The Schema defines all the fields that exist for an Account object.

List Account Segments via GET /accountSegments. Returns all Account Segments available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Account Segment via GET /accountSegments/{account_segment_id}. This endpoint retrieves data of a specific Account Segment based on JSON input. The API returns a single Account Segment available to the user in the Value List, according to the unique ID provided. If the specified Account Segment does not exist, the response will be a "bad request".

Account Segments schema via GET /accountSegments/schema. Returns properties object with the definition of each field in the Account Segment table. With the Account Segment you can differentiate the Account based on specific visit cycles, hence assigning a priority to each Account.

List Related Accounts via GET /accountsRelated. Returns all Related Accounts available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Retrieve Related Account via GET /accountsRelated/{related_account_id}. This endpoint retrieves data of a specific Related Account based on JSON input. The API returns a single Related Account available to the user, according to the unique ID provided. If the specified Related Account does not exist, the response will be a "bad request".

Related Accounts schema via GET /accountsRelated/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The schema defines all the fields that exist for a Related Account object.

List Related Account Types via GET /accountsRelations. Returns all Related Account Types available, based on JSON input. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation.

Retrieve Related Account Type via GET /accountsRelations/{related_account_type_id}. This endpoint retrieves data of a specific Related Account Type based on JSON input. The API returns a single Type available to the user in the Value List, according to the unique ID provided. If the specified Related Account Type does not exist, the response will be a "bad request".

Related Account Types schema via GET /accountsRelations/schema. Returns properties object with the definition of each field in the Related Account Type table. With the Related Account Type you can differentiate the Type of Relation.

List Account Statuses via GET /accountStatuses. Returns all Account Statuses available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Account Status via GET /accountStatuses/{account_status_id}. This endpoint retrieves data of a specific Account Status based on JSON input. The API returns a single Account Status available to the user in the Value List, according to the unique ID provided. If the specified Account Status does not exist, the response will be a "bad request".

Account Statuses schema via GET /accountStatuses/schema. Returns properties object with the definition of each field in the Account Status table.

List Account Types via GET /accountTypes. Returns all Account Types available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Account Type via GET /accountTypes/{account_type_id}. Returns one Account Type by its integer id. An Account Type carries its translated descriptions, its branch visibility, and the computeSfm and internal flags that decide whether it counts for sales analytics and whether it is for internal use only. The sealed contract documents this operation with a RESPONSE table and no prose of its own; this description is authored from that table. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Account Types schema via GET /accountTypes/schema. Returns properties object with the definition of each field in the Account Type table.

List Activities via GET /activities. Returns all Activities available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Activity via GET /activities/{activity_id}. This endpoint retrieves data of a specific Activity based on JSON input. The API returns a single Activity available to the user, according to the unique ID provided. If the specified Activity does not exist, the response will be a "bad request". `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Activities schema via GET /activities/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The schema defines all the fields that exist for an Activity object.

List Activity Points via GET /activity/points. Returns all Activity Points available in the user's ForceManager implementation database.

List Activity Types via GET /activityTypes. Returns all Activity Types available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Activity Type via GET /activityTypes/{activity_type_id}. This endpoint retrieves data of a specific Activity Type based on JSON input. The API returns a single Type available to the user in the Value List, according to the unique ID provided. If the specified Activity Type does not exist, the response will be a "bad request".

Activity Types schema via GET /activityTypes/schema. Returns properties object with the definition of each field in the Activity Type table. With the Activity Type you can differentiate the Type of Activity with which professional relationships are stablished.

List Branches via GET /branches. Returns all Branches.

Get Branch via GET /branches/{branch_id}. This endpoint retrieves data of a specific Branch based on JSON input. The API returns a single Branch available to the user in the Value List, according to the unique ID provided. If the specified Branch does not exist, the response will be a "bad request".

Branches schema via GET /branches/schema. Returns properties object with the definition of each field in the Branches table.

List Calendar via GET /calendar. Returns all Events and Tasks available in the user's ForceManager implementation database based on JSON input. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Calendar via GET /calendar/{calendar_entry_id}. This endpoint retrieves data of a specific calendar Event or Task based on JSON input. The API returns a single Type available to the user, according to the unique ID provided. If the specified calendar Event or Task does not exist, the response will be a "bad request". `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Calendar schema via GET /calendar/schema. The Schema is a metadata that tells you how the data is structured for a specific resource. The schema defines all the fields that exist for a Event/Task object. Returns properties object with the definition of each field in the Event/Task table.

List Calls via GET /calls. Returns all Calls available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation.

Get Call via GET /calls/{call_id}. This endpoint retrieves data of a specific Call based on JSON input. The API returns a single Call available to the user, according to the unique ID provided. If the specified Call does not exist, the response will be a "bad request".

Get Resources by Phone Number via GET /calls/phone/{phone_number}. Returns the ids of the Contacts, Accounts and Users associated with a specific phone number -- the vendor's own one-line account of this route, from the Calls API method table ('Get a list of Contacts, Accounts, Users IDs referred to a specific phone number'). It is a lookup, not a read of a Call: pass the phone number in the path. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

List Campaign Questions via GET /campaignQuestions. Returns all Campaign Questions available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Campaign Question via GET /campaignQuestions/{question_id}. This endpoint retrieves data of a specific Campaign Question based on JSON input. The API returns a single Campaign Question available to the user, according to the unique ID provided. If the specified Campaign Question does not exist, the response will be a "bad request".

List Question Answers via GET /campaignQuestions/{question_id}/answers. Returns all Campaign Question Answers available in the user's ForceManager implementation database. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Question Answer via GET /campaignQuestions/{question_id}/answers/{answer_id}. This endpoint retrieves data of a specific Campaign Question Answer based on JSON input. The API returns a single Campaign Question Answer available to the user, according to the unique ID provided. If the specified Campaign Question Answer does not exist, the response will be a "bad request".

List Question Values via GET /campaignQuestions/{question_id}/values. Returns all Campaign Question Values available in the user's ForceManager implementation database. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Question Value via GET /campaignQuestions/{question_id}/values/{value_id}. This endpoint retrieves data of a specific Campaign Question Value based on JSON input. The API returns a single Campaign Question Value available to the user, according to the unique ID provided. If the specified Campaign Question Value does not exist, the response will be a "bad request".

List Campaigns via GET /campaigns. Returns all Campaigns available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Campaign via GET /campaigns/{campaign_id}. This endpoint retrieves data of a specific Campaign based on JSON input. The API returns a single Campaign available to the user, according to the unique ID provided. If the specified Campaign does not exist, the response will be a "bad request".

List Campaign Accounts via GET /campaigns/{campaign_id}/entities. Returns all Campaign Accounts available in the user's ForceManager implementation database. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Campaign Account via GET /campaigns/{campaign_id}/entities/{entity_id}. This endpoint retrieves data of a specific Campaign Account based on JSON input. The API returns a single Campaign Account available to the user, according to the unique ID provided. If the specified Campaign Account does not exist, the response will be a "bad request".

List Campaign Statuses via GET /campaignStatuses. Returns all Campaign Statuses available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

List Contacts via GET /contacts. Returns all Contacts available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Contact via GET /contacts/{contact_id}. This endpoint retrieves data of a specific Contact based on JSON input. The API returns a single Contact available to the user, according to the unique ID provided. If the specified Contact does not exist, the response will be a "bad request".

Contacts schema via GET /contacts/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The schema defines all the fields that exist for a Contact object.

List Entity Contacts via GET /contactsEntities. Returns all Entity Contacts available. Entity Contacts are basically needed to associate more than one User to an Entity (e.g. the Opportunities with more than one sales rep).

Entity Contacts schema via GET /contactsEntities/schema. Returns properties object with the definition of each field in the Entity Contacts table.

List Contact Types via GET /contactTypes. Returns all Contact Types available in the user's ForceManager implementation database. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Contact Type via GET /contactTypes/{contact_type_id}. This endpoint retrieves data of a specific Contact Type based on JSON input. The API returns a single Contact Type available to the user in the Value List, according to the unique ID provided. If the specified Contact Type does not exist, the response will be a "bad request".

Contact Types schema via GET /contactTypes/schema. Returns properties object with the definition of each field in the Contact Types table.

List Countries via GET /countries. Returns all Countries available. Countries are basically needed for the geolocalized data (e.g. Accounts, Opportunities, Activities) in which a full address need to be specified.

Countries schema via GET /countries/schema. Returns properties object with the definition of each field in the Countries table.

List Currencies via GET /currencies. Returns all Currencies available. Currencies are needed for defining the measurement unit of the Opportunities.

Currencies schema via GET /currencies/schema. Returns properties object with the definition of each field in the Currencies table.

List Documents via GET /documents. Returns all Documents available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

List Folders via GET /documents/folders. Returns all Folders available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

List Emails via GET /emails. Returns all Emails available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation.

Get Email via GET /emails/{email_id}. This endpoint retrieves data of a specific Email based on JSON input. The API returns a single Email available to the user, according to the unique ID provided. If the specified Email does not exist, the response will be a "bad request".

Emails schema via GET /emails/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The schema defines all the fields that exist for a Email object.

List Entity Owners via GET /entityOwners. Returns all Entity Owners available. Entity Owners are basically needed to associate more than one User to an Entity (e.g. the Opportunities with more than one sales rep).

Entity Owners schema via GET /entityOwners/schema. Returns properties object with the definition of each field in the Entity Owners table.

List Extra Fields by Resource via GET /extrafields/{resource}. Returns all Extra Fields available in the user's ForceManager implementation database, for a specific Entity. `resource` is the entity name in the first path segment; the vendor documents `accounts`, `activities`, `calendar`, `contacts`, `opportunities`, `products`, `rates`, `salesorders`, `users` -- the one place the vendor writes 'The allowed values are'. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Extra Fields schema by Resource via GET /extrafields/{resource}/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The schema defines all the fields that exist for an Extra Field object. `resource` is the entity name in the first path segment; the vendor documents `accounts`, `activities`, `calendar`, `contacts`, `opportunities`, `products`, `rates`, `salesorders`, `users`. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

List Tabs via GET /extrafieldsTabs. Returns all Tabs available. Tabs are needed for grouping together Extra Fields of each entity.

Get Tabs via GET /extrafieldsTabs/{tab_id}. This endpoint retrieves data of a specific Tab based on JSON input. The API returns a single Tab available, according to the unique ID provided. If the specified Tab does not exist, the response will be a "bad request".

Get Form via GET /forms/{form_id}. This endpoint retrieves data of a specific Form based on JSON input. The API returns a single Form available to the user, according to the unique ID provided. If the specified Form does not exist, the response will be a "bad request".

Get Form State via GET /forms/{form_id}/state. This endpoint retrieves data of a specific Form State based on JSON input. The API returns a single Form State available to the user, according to the unique ID provided. If the specified Form State does not exist, the response will be a "bad request".

Get Form Template via GET /forms/{form_id}/template. This endpoint retrieves data of a specific Form Template based on JSON input. The API returns a single Form Template available to the user, according to the unique ID provided. If the specified Form Template does not exist, the response will be a "bad request".

List Webhooks via GET /hooks. Returns all Webhooks available in the user's ForceManager implementation database.

Get Webhook via GET /hooks/{webhook_id}. This endpoint retrieves data of a specific Webhook based on JSON input. The API returns a single Webhook available, according to the unique ID provided. If the specified Webhook does not exist, the response will be a "bad request".

List Lists via GET /list. Returns all Lists available in the user's ForceManager implementation database based on JSON input.

List Values via GET /list/{list_name}. Returns all Values for the Value List available in the user's ForceManager implementation database based on JSON input. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Get Value via GET /list/{list_name}/{value_id}. This endpoint retrieves data of a specific Value from a specific Value List based on JSON input. The API returns a single Value available to the user in the Value List, according to the unique ID provided. If the specified Value or Value List do not exist, the response will be a "bad request".

Values List schema via GET /list/{list_name}/schema. The Value List API provides a simple interface to manage your extra or customised Value Lists. Value Lists are personalised and predetermined values that help you unify criteria when entering data into a field and help organise these elements. The Schema is metadata that tells you how the data is structured for this specific customised Value List. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

List News via GET /news. Returns all News available. News are basically messages that you can sent to the whole organization, to your team or to an User. These messages can be tracked in terms of the number of Users that had received, open or read it.

List Opportunities via GET /opportunities. Returns all Opportunities available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Opportunity via GET /opportunities/{opportunity_id}. This endpoint retrieves data of a specific Opportunity based on JSON input. The API returns a single Opportunity available to the user, according to the unique ID provided. If the specified Opportunity does not exist, the response will be a "bad request".

Opportunities schema via GET /opportunities/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The Schema defines all the fields that exist for an Opportunity object.

List Opportunity Statuses via GET /opportunityStatuses. Returns all Opportunity Statuses available in the user's ForceManager implementation database.

Get Opportunity Status via GET /opportunityStatuses/{opportunity_status_id}. This endpoint retrieves data of a specific Opportunity Status based on JSON input. The API returns a single Opportunity Status available to the user in the Value List, according to the unique ID provided. If the specified Opportunity Status does not exist, the response will be a "bad request".

Opportunity Statuses schema via GET /opportunityStatuses/schema. Returns properties object with the definition of each field in the Opportunity Status table.

List Opportunity Types via GET /opportunityTypes. Returns all Opportunity Types available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Opportunity Types via GET /opportunityTypes/{opportunity_type_id}. This endpoint retrieves data of a specific Opportunity Type based on JSON input. The API returns a single Opportunity Type available to the user in the Value List, according to the unique ID provided. If the specified Opportunity Type does not exist, the response will be a "bad request".

Opportunity Types schema via GET /opportunityTypes/schema. Returns properties object with the definition of each field in the Opportunity Types table.

List Order Types via GET /orderTypes. Returns all Orders Types available.

Get Order Types via GET /orderTypes/{order_type_id}. This endpoint retrieves data of a specific Order Types based on JSON input. The API returns a single Type available to the user in the Value List, according to the unique ID provided. If the specified Order Types does not exist, the response will be a "bad request".

Order Types schema via GET /orderTypes/schema. The Schema is metadata that tells you how the data is structured for this specific Value list.

List Product Categories via GET /productCategories. Returns all Product Categories available. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation.

Get Product Category via GET /productCategories/{product_category_id}. This endpoint retrieves data of a specific Product Category based on JSON input. The API returns a single Product Category available to the user in the Value List, according to the unique ID provided. If the specified Category does not exist, the response will be a "bad request".

Product Categories schema via GET /productCategories/schema. Returns properties object with the definition of each field in the Product Categories table. With the Product Category you can classify each Product.

List Product Families via GET /productFamilies. Returns all Product Families available. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation.

Get Product Family via GET /productFamilies/{product_family_id}. This endpoint retrieves data of a specific Product Family based on JSON input. The API returns a single Product Family available to the user in the Value List, according to the unique ID provided. If the specified Family does not exist, the response will be a "bad request".

Product Families schema via GET /productFamilies/schema. Returns properties object with the definition of each field in the Product Families table. With the Product Family you can classify each Product.

List Product Rates via GET /productRates. Returns all Product Rates available. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation.

Get Product Rate via GET /productRates/{product_rate_id}. This endpoint retrieves data of a specific Product Rate based on JSON input. The API returns a single Product Rate available to the user in the Value List, according to the unique ID provided. If the specified Rate does not exist, the response will be a "bad request".

Product Rates schema via GET /productRates/schema. Returns properties object with the definition of each field in the Product Rates table. With the Product Rate you can associate a Rate to each Product.

List Products via GET /products. Returns all Products available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Product via GET /products/{product_id}. This endpoint retrieves data of a specific Product based on JSON input. The API returns a single Product available to the user, according to the unique Product ID provided. If the specified Product does not exist, the response will be a "bad request". `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Products schema via GET /products/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The Schema defines all the fields that exist for a Product object.

List Rates via GET /rates. Returns all Rates available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation.

Get Rate via GET /rates/{rate_id}. This endpoint retrieves data of a specific Rate based on JSON input. The API returns a single Rate available to the user, according to the unique ID provided. If the specified Rate does not exist, the response will be a "bad request".

Rates schema via GET /rates/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The schema defines all the fields that exist for a Rate object.

List Documents of a Resource via GET /{resource}/{resource_id}/documents. Returns all Documents associated to the specific Resource (accounts, opportunities, salesOrders, ...) available in the user's ForceManager implementation database based on JSON input. `resource` is the entity name in the first path segment; the vendor documents `accounts`, `opportunities`, `salesOrders`, and the vendor's list ends in an ellipsis, so it is not exhaustive. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

List Folders of a Resource via GET /{resource}/{resource_id}/documents/folders. Returns all Folders of a specific Entity available in the user's ForceManager implementation database. `resource` is the entity name in the first path segment; the vendor documents `accounts`, `opportunities`, `salesOrders`, and the vendor's list ends in an ellipsis, so it is not exhaustive. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

List Warnings of a Resource via GET /{resource}/{resource_id}/warnings. Returns all Warnings associated to the specific Resource (accounts, opportunities, products, salesorders) available in the user's ForceManager implementation database. `resource` is the entity name in the first path segment; the vendor documents `accounts`, `opportunities`, `products`, `salesorders`. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Get Resources via GET /resources. This endpoint retrieves all the methods available in the API on JSON input.

List Roles via GET /roles. Returns all Roles available in the user's ForceManager account database based on JSON input. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation.

Get Role via GET /roles/{role_id}. This endpoint retrieves data of a specific Role based on JSON input. The API returns a single Role available to the user, according to the unique ID provided. If the specified Role does not exist, the response will be a "bad request".

List Users in Role via GET /roles/{role_id}/users. Returns all Users assigned to the specific Role available in the user's ForceManager implementation database. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Roles schema via GET /roles/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The schema defines all the fields that exist for a Roles object.

List Sales via GET /sales. Returns all Sales available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Sale via GET /sales/{sale_id}. This endpoint retrieves data of a specific Sale based on JSON input. The API returns a single Sale available to the user, according to the unique ID provided. If the specified Sale does not exist, the response will be a "bad request".

Sales schema via GET /sales/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The schema defines all the fields that exist for a Sales object. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

List Order Headers via GET /salesorders. Returns all Order Headers available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Order Header via GET /salesorders/{order_id}. This endpoint retrieves data of a specific Order Header based on JSON input. The API returns a single Header available to the user, according to the unique ID provided. If the specified Order Header does not exist, the response will be a "bad request".

Order Headers schema via GET /salesorders/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The Schema defines all the fields that exist for an Order Header object.

List Order Lines via GET /salesordersLines. Returns all Orders Lines available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get Order Line via GET /salesordersLines/{order_line_id}. This endpoint retrieves data of a specific Order Line based on JSON input. The API returns a single Line available to the user, according to the unique ID provided. If the specified Order Line does not exist, the response will be a "bad request".

Order Lines schema via GET /salesordersLines/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The Schema defines all the fields that exist for an Order Line object.

List Order Statuses via GET /salesorderStatuses. Returns all Orders Statuses available.

Get Order Status via GET /salesorderStatuses/{order_status_id}. This endpoint retrieves data of a specific Order Status based on JSON input. The API returns a single Status available to the user in the Value List, according to the unique ID provided. If the specified Order Status does not exist, the response will be a "bad request".

Order Statuses schema via GET /salesorderStatuses/schema. The Schema is metadata that tells you how the data is structured for this specific Value list.

List TimeZones via GET /timezones. Returns all TimeZones available.

List Users via GET /users. Returns all Users available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get User via GET /users/{user_id}. This endpoint retrieves data of a specific User based on JSON input. The API returns a single User available to the user, according to the unique ID provided. If the specified User does not exist, the response will be a "bad request".

List User Hierarchy via GET /users/{user_id}/hierarchy. This endpoint retrieves the hierarchy of a User based on JSON input. Specifically, an array of JSON data is returned, that reports the id and the name of each user that are below the requested User, on a hierarchical perspective. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

List Roles of User via GET /users/{user_id}/roles. Returns all the Roles assigned to the user in ForceManager account database based on JSON input. <br> An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Users schema via GET /users/schema. The Schema is metadata that tells you how the data is structured for a specific resource. The schema defines all the fields that exist for a User object.

List Users Scores via GET /users/scores. This endpoint retrieves the activity and sales Scores of the Users - which measured via the ForceActivity algorithm - based on JSON input. Specifically, an array of JSON data is returned.

List User Types via GET /userTypes. Returns all User Types available in the user's ForceManager implementation database. `count` is sent as the `Count` header and sets the page SIZE (default 50); this build ships no page selector, because the converted contract declares no query parameter on any operation. `extra_field_description` is sent as the `ExtraFieldDescription` header: 0 returns Extra Field values only, 1 their descriptions too.

Get User Type via GET /userTypes/{user_type_id}. This endpoint retrieves data of a specific User Type based on JSON input. The API returns a single User Type available to the user in the Value List, according to the unique ID provided. If the specified User Type does not exist, the response will be a "bad request".

User Types schema via GET /userTypes/schema. Returns properties object with the definition of each field in the User Type table.

Create Account Address via POST /accountAddresses. This endpoint allows you to create an Account Address based on JSON input.

Create Account via POST /accounts. This endpoint allows you to create a Account based on JSON input.

Create Account Segment via POST /accountSegments. This endpoint allows you to create a Account Segment based on JSON input.

Create Related Account via POST /accountsRelated. This endpoint allows you to create a Related Account based on JSON input.

Create Related Account Type via POST /accountsRelations. This endpoint allows you to create a Related Account Type based on JSON input.

Create Account Status via POST /accountStatuses. This endpoint allows you to create a Account Status based on JSON input.

Create Account Type via POST /accountTypes. This endpoint allows you to create a Account Type based on JSON input.

Create Activity via POST /activities. This endpoint allows you to create an Activity based on JSON input.

Create Activity Type via POST /activityTypes. This endpoint allows you to create an Activity Type based on JSON input.

Create Calendar via POST /calendar. This endpoint allows you to create a Event/Task based on JSON input.

Create Call by User ID via POST /calls. This endpoint allows you to create a Call based on JSON input, providing the ForceManager User ID to whom the Call has to be associated.

Create Call by User Phone Number via POST /calls/identify. This endpoint allows you to create a Call based on JSON input, providing as an identifier of the ForceManager User its email instead of the ID. This endpoint is useful in the case in which the external system (e.g. a PBX) is not aware of the ForceManager User ID but it has the reference of all the Users' phone numbers.

Create Campaign Question via POST /campaignQuestions. This endpoint allows you to create a Campaign Question based on JSON input.

Create Question Answer via POST /campaignQuestions/{question_id}/answers. This endpoint allows you to create a Campaign Question Answer based on JSON input. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Create Question Value via POST /campaignQuestions/{question_id}/values. This endpoint allows you to create a Campaign Question Value based on JSON input. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Create Campaign via POST /campaigns. This endpoint allows you to create a Campaign based on JSON input.

Create Campaign Account via POST /campaigns/{campaign_id}/entities/{entity_id}. Links an Account to this Campaign, creating the Campaign Account record. If the specified Campaign or Account does not exist, the response is a bad request.

Create Contact via POST /contacts. This endpoint allows you to create a Contact based on JSON input.

Create Contact Type via POST /contactTypes. This endpoint allows you to create a Contact Type based on JSON input.

Add Document via POST /documents. This endpoint allows you to upload a Document based on JSON input. FIRST STEP ONLY: ForceManager answers with a `locator` URL the file must then be PUT to. This integration ships no binary channel, so it registers the document and returns that URL; moving the bytes is the caller's.

Create Folder via POST /documents/folders. This endpoint allows you to create a Folder based on JSON input.

Create Email via POST /emails. This endpoint allows you to create an Email based on JSON input.

Create Extra Field for Resource via POST /extrafields/{resource}. This endpoint allows you to create an Extra Field for a specific entity. `resource` is the entity name in the first path segment; the vendor documents `accounts`, `activities`, `calendar`, `contacts`, `opportunities`, `products`, `rates`, `salesorders`, `users` -- the one place the vendor writes 'The allowed values are'. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Create Tabs via POST /extrafieldsTabs. This endpoint allows you to create a Tab based on JSON input.

Create Webhook via POST /hooks. This endpoint allows you to create an Webhook based on JSON input.

Create List via POST /list. This endpoint allows you to create a List based on JSON input.

Create Value via POST /list/{list_name}. This endpoint allows you to create a single Value or a complete Value List based on JSON input. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Create Opportunity via POST /opportunities. This endpoint allows you to create a Opportunity based on JSON input.

Create Opportunity Status via POST /opportunityStatuses. This endpoint allows you to create a Opportunity Status based on JSON input.

Create Opportunity Type via POST /opportunityTypes. This endpoint allows you to create a Opportunity Status based on JSON input.

Create Order Types via POST /orderTypes. This endpoint allows you to create an Order Types based on JSON input.

Create Product Category via POST /productCategories. This endpoint allows you to create a Product Category based on JSON input.

Create Product Family via POST /productFamilies. This endpoint allows you to create a Product Family based on JSON input.

Create Product Rate via POST /productRates. This endpoint allows you to create a Product Rate based on JSON input.

Create Product via POST /products. This endpoint allows you to create a Product based on JSON input.

Bulk Create Products via POST /products/bulk. This endpoint allows you to create Multiple Products (100 entities for request) based on JSON input.

Add Picture via POST /products/{product_id}/documents. This endpoint allows you to upload a Picture based on JSON input. FIRST STEP ONLY: ForceManager answers with a `locator` URL the file must then be PUT to. This integration ships no binary channel, so it registers the document and returns that URL; moving the bytes is the caller's. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Create Rate via POST /rates. This endpoint allows you to create a Rate based on JSON input.

Bulk Create Resources via POST /{resource}/bulk. This endpoint allows you to create multiple Resources (200 entities for request) based on JSON input. `resource` is the entity name in the first path segment; the vendor documents Accounts, Contacts, Opportunities, Orders and Value Lists are the examples the vendor gives ('e.g.'), so the list is not exhaustive. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Add Document to a Resource via POST /{resource}/{resource_id}/documents. This endpoint allows you to upload a Document linking it to a Resource (accounts, opportunities, salesOrders) based on JSON input. `resource` is the entity name in the first path segment; the vendor documents `accounts`, `opportunities`, `salesOrders`, and the vendor's list ends in an ellipsis, so it is not exhaustive. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged. FIRST STEP ONLY: ForceManager answers with a `locator` URL the file must then be PUT to. This integration ships no binary channel, so it registers the document and returns that URL; moving the bytes is the caller's. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Create Folder for a Resource via POST /{resource}/{resource_id}/documents/folders. This endpoint allows you to create a Folder for a specific Entity based on JSON input. `resource` is the entity name in the first path segment; the vendor documents `accounts`, `opportunities`, `salesOrders`, and the vendor's list ends in an ellipsis, so it is not exhaustive. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Create Warning for a Resource Copy via POST /{resource}/{resource_id}/warnings. This endpoint allows you to create a Warning in the specific Resource (accounts, opportunities, products, salesorders) based on JSON input. `resource` is the entity name in the first path segment; the vendor documents `accounts`, `opportunities`, `products`, `salesorders`. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Create Sale via POST /sales. This endpoint allows you to create a Sales based on JSON input.

Create Order Header via POST /salesorders. This endpoint allows you to create am Order Header based on JSON input.

Create Order Line via POST /salesOrdersLines. This endpoint allows you to create Orders Lines based on JSON input.

Create Order Status via POST /salesorderStatuses. This endpoint allows you to create an Order Status based on JSON input.

Create User via POST /users. This endpoint allows you to create a User based on JSON input. `password` in the body is the NEW ForceManager user's own sign-in password, not this connection's credential.

Create User Type via POST /userTypes. This endpoint allows you to create a User Type based on JSON input.

Update Account Address via PUT /accountAddresses/{account_address_id}. This endpoint allows you to update a specific Account Address. If the specified Address does not exist, the response will be a "bad request".

Update Account via PUT /accounts/{account_id}. This endpoint allows you to update a specific Account. If the specified Account does not exist, the response will be a "bad request".

Update Account Segment via PUT /accountSegments/{account_segment_id}. This endpoint allows you to update a specific Account Segment. If the specified Account Segment does not exist, the response will be a "bad request".

Update Related Account via PUT /accountsRelated/{related_account_id}. The endpoint allows you to update a specific Related Account information from the user's ForceManager implementation database. If the specified Related Account does not exist, the response will be a "bad request".

Update Related Account Type via PUT /accountsRelations/{related_account_type_id}. This endpoint allows you to update a specific Related Account Type. If the specified Type does not exist, the response will be a "bad request".

Update Account Status via PUT /accountStatuses/{account_status_id}. This endpoint allows you to update a specific Account Status. If the specified Account Status does not exist, the response will be a "bad request".

Update Activity via PUT /activities/{activity_id}. This endpoint allows you to update a specific Activity. If the specified Activity does not exist, the response will be a "bad request".

Update Activity Points via PUT /activity/points. This endpoint allows you to update one or more Activity Points.

Update Activity Type via PUT /activityTypes/{activity_type_id}. This endpoint allows you to update a specific Activity Type. If the specified Type does not exist, the response will be a "bad request".

Update Calendar via PUT /calendar/{calendar_entry_id}. The endpoint allows you to update specific information of a calendar Event or Task from the user's ForceManager implementation database. If the specified Event or Task does not exist, the response will be a "bad request".

Update Call via PUT /calls/{call_id}. This endpoint allows you to update specific information of a Call. If the specified Call does not exist, the response will be a "bad request".

Update Campaign Question via PUT /campaignQuestions/{question_id}. This endpoint allows you to update a specific Campaign Question. If the specified Campaign Question does not exist, the response will be a "bad request".

Update Question Answer via PUT /campaignQuestions/{question_id}/answers/{answer_id}. This endpoint allows you to update a specific Campaign Question Answer. If the specified Campaign Question Answer does not exist, the response will be a "bad request".

Update Question Value via PUT /campaignQuestions/{question_id}/values/{value_id}. This endpoint allows you to update a specific Campaign Question Value. If the specified Campaign Question Value does not exist, the response will be a "bad request".

Update Campaign via PUT /campaigns/{campaign_id}. This endpoint allows you to update a specific Campaign. If the specified Campaign does not exist, the response will be a "bad request".

Update Campaign Account via PUT /campaigns/{campaign_id}/entities/{entity_id}. This endpoint allows you to update a specific Campaign Account. If the specified Campaign Account does not exist, the response will be a "bad request".

Update Contact via PUT /contacts/{contact_id}. This endpoint allows you to update a specific Contact. If the specified Contact does not exist, the response will be a "bad request".

Update Contact Type via PUT /contactTypes/{contact_type_id}. This endpoint allows you to update a specific Contact Type. If the specified Contact Type does not exist, the response will be a "bad request".

Update Tabs via PUT /extrafieldsTabs/{tab_id}. This endpoint allows you to update a specific Tab's information. If the specified Tab does not exist, the response will be a "bad request".

Update Webhook via PUT /hooks/{webhook_id}. This endpoint allows you to update a specific Webhook's information. If the specified Webhook does not exist, the response will be a "bad request".

Update Account Type via PUT /list/accountTypes/{account_type_id}. This endpoint allows you to update a specific Account Type. If the specified Account Type does not exist, the response will be a "bad request".

Update List via PUT /list/{list_name}. This endpoint allows you to update a specific List's information. If the specified List does not exist, the response will be a "bad request".

Update Value via PUT /list/{list_name}/{value_id}. This endpoint allows you to update a specific Value List's information. If the specified Value does not exist, the response will be a "bad request".

Update Opportunity via PUT /opportunities/{opportunity_id}. This endpoint allows you to update a specific Opportunity. If the specified Opportunity does not exist, the response will be a "bad request".

Update Opportunity Status via PUT /opportunityStatuses/{opportunity_status_id}. This endpoint allows you to update a specific Opportunity Status. If the specified Opportunity Status does not exist, the response will be a "bad request".

Update Opportunity Type via PUT /opportunityTypes/{opportunity_type_id}. This endpoint allows you to update a specific Opportunity Status. If the specified Opportunity Status does not exist, the response will be a "bad request".

Update Order Types via PUT /orderTypes/{order_type_id}. This endpoint allows you to update a specific Order Types. If the specified Types does not exist, the response will be a "bad request".

Update Product Category via PUT /productCategories/{product_category_id}. This endpoint allows you to update a specific information of a Product Category. If the specified Type does not exist, the response will be a "bad request".

Update Product Family via PUT /productFamilies/{product_family_id}. This endpoint allows you to update a specific information of a Product Family. If the specified Type does not exist, the response will be a "bad request".

Update Product Rate via PUT /productRates/{product_rate_id}. This endpoint allows you to update a specific information of a Product Rate. If the specified Type does not exist, the response will be a "bad request".

Bulk Update Products via PUT /products/bulk. This endpoint allows you to update a Multiple Products (100 entities for request) information from the user's ForceManager implementation database. In order to update Multiple Products, you just have to specify the attributes you want to modify and complete with the up to date information. It is not necessary to send all attributes.

Update Product via PUT /products/{product_id}. This endpoint allows you to update specific information of a Product from the user's ForceManager implementation database. If the specified Product does not exist, the response will be a "bad request".

Update Rate via PUT /rates/{rate_id}. This endpoint allows you to update specific information of a Rate. If the specified Rate does not exist, the response will be a "bad request".

Bulk Update Resources via PUT /{resource}/bulk. This endpoint allows you to update a multiple Resources (200 entities for request) information from the user's ForceManager implementation database. In order to update multiple Resources, you just have to specify the attributes you want to modify and complete with the up to date information. It is not necessary to send all attributes. `resource` is the entity name in the first path segment; the vendor documents Accounts, Contacts, Opportunities, Orders and Value Lists are the examples the vendor gives ('e.g.'), so the list is not exhaustive. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Update Warning of a Resource via PUT /{resource}/{resource_id}/warnings/{warning_id}. This endpoint allows you to update a Warning in the specific Resource (accounts, opportunities, products, salesorders) based on JSON input. <br> `resource` is the entity name in the first path segment; the vendor documents `accounts`, `opportunities`, `products`, `salesorders`. That is prose, not a schema -- its capitalisation differs between the vendor's own articles -- so the value is passed through unchanged. An id that does not exist answers 400, not 404 (the vendor's own wording), so read the error body rather than the status.

Update Sale via PUT /sales/{sale_id}. The endpoint allows you to update a specific Sale information from the user's ForceManager implementation database. If the specified Contact does not exist, the response will be a "bad request".

Update Order Header via PUT /salesorders/{order_id}. This endpoint allows you to update a specific Order Header. If the specified Header does not exist, the response will be a "bad request".

Update Order Line via PUT /salesordersLines/{order_line_id}. This endpoint allows you to update a specific Order Line. If the specified Line does not exist, the response will be a "bad request".

Update Order Status via PUT /salesorderStatuses/{order_status_id}. This endpoint allows you to update a specific Order Status. If the specified Status does not exist, the response will be a "bad request".

Update User via PUT /users/{user_id}. This endpoint allows you to update a specific User. If the specified User does not exist, the response will be a "bad request".

Add Roles in User via PUT /users/{user_id}/roles. This endpoint allows you to update a specific User's Roles information from the user's ForceManager account database. If the specified User does not exist, the response will be a "bad request". In order to update the User's Roles, you just have to specify the Role you want to add at.

Update User Type via PUT /userTypes/{user_type_id}. This endpoint allows you to update a specific User Type. If the specified User Type does not exist, the response will be a "bad request".