--- title: "List Activity Types" method: GET path: "/activityTypes" tags: ["Activities / Types"] --- # List Activity Types `GET /activityTypes` ## Request - Base URL: `https://api.forcemanager.com/api/v4` - URL: `https://api.forcemanager.com/api/v4/activityTypes` - Auth: API key in header `X-Session-Key` Returns all Activity Types available in the user's ForceManager implementation database. You will only receive the List of Activity Types after first providing the Session Key. To know how you can obtain the Session Key, [go to Authentication](#tag/authentication/POST/login). **HEADERS** | **Parameter** | **Value** | **Description** | | --- | --- | --- | | Content-Type | application/json | Language in which all request and response bodies are encoded | | Accept | \*/\* | Any data of whatever mime type is accepted | | X-Session-Key | AUTH_TOKEN | This field must be completed with the token obtained at the authentication | | Count | {number} | The number of records to return in each page of results. The default page limit is 50 | | ExtraFieldDescription | {number} | If equal to "0", the response returns only the value of each Extra Fields, if equal to "1" also the description is returned | **REQUEST** You can apply filters, organise and choose the language and pagination using any query string parameter in SQL. Query string parameters appear after a question mark in the endpoint followed by the parameters and their values. In the query string, each parameter is listed one right after the other with an `AND` separating them. The order of the parameters does not matter. | **Parameter** | **Type** | **Description** | | --- | --- | --- | | page | Integer | Define the pagination data for the returned objects | | param1, param2... | String, Integer | Apply filters using any query string parameter in SQL | | order | String | organise and view the results for a specific attribute in descendent order - at the top the most recent results while the oldest results will be down the list | | lang | String | Define the language in which you want to receive the response | You can define the **pagination** data for the returned objects. The default page number is 0, otherwise you can optionally determine the page number. e.g. ``` https://api.forcemanager.com/api/v4/activityTypes?page=PAGE_NUMBER ``` You can **apply filters**. e.g. ``` https://api.forcemanager.com/api/v4/activityTypes?where= param1=value AND/OR param2=value2 ``` You can also **organise and view** the results for Activity Types in descendent order - at the top, the most recent results while the oldest results will be down the list. e.g. ``` https://api.forcemanager.com/api/v4/activityTypes?order=VALUE ``` In the request, and using query string parameters, you can also define the **language** in which you want to receive the response. e.g. ``` https://api.forcemanager.com/api/v4/activityTypes?lang=VALUE ``` **RESPONSE** This endpoint returns information about all Activity Types available in the database. If you didn't apply any page or count number in the header the default number of records in the response is 50. List of the supported Activity Types attributes: | **Attribute** | **Type** | **Description** | | --- | --- | --- | | branchVisibility | Array, Null | In which Branches the Activity Type is visible | | descriptionBR | String | Activity Type name in Brasilian Portuguese | | descriptionDE | String | Activity Type name in German | | descriptionDK | String | Activity Type name in Dutch | | descriptionEN | String | Activity Type name in English | | descriptionES | String | Activity Type name in Spanish | | descriptionFR | String | Activity Type name in French | | descriptionIT | String | Activity Type name in Italian | | descriptionPT | String | Activity Type name in Portuguese | | descriptionRU | String | Activity Type name in Russian | | descriptionUS | String | Activity Type name in American English | | general | Boolean | If true, this Activity Type will appear when adding a normal Activity | | checkin | Boolean | If true, this Activity Type will appear when doing a check-in | | fastCheckin | Boolean | If true, this Activity Type will appear when doing a fast check-in | | phoneCall | Boolean | If true, the Activity Type is a phone call | | visit | Boolean | If true, the Activity Type is a visit | | videoCall | Boolean | If true, the Activity Type is a video call | | visibleInActivities | Boolean | If true, the Activity Type is visible in the activity feed | | visibleInAgendaActivities | Boolean | If true, the Activity Type is visible in the calendar | | workflow | Boolean | If true, the Activity Type is visible in workflows | | id | Integer | Unique identifier for the Activity Type in ForceManager | | order | Integer | The position in what you want the Activity Type to appear in the list | | salesRepIdCreated | Integer | Unique identifier of the user who created the Activity Type | | salesRepIdDeleted | Integer | Unique identifier of the user who deleted the Activity Type | | salesRepIdUpdated | Integer | Unique identifier of the user who last updated the Activity Type | | dateCreated | String | Date and time when the Activity Type was created | | dateDeleted | String | Date and time when the Activity Type was deleted | | dateUpdated | String | Date and time when the Activity Type was last updated | | deleted | Boolean | If true, the branch has been deleted and archived | | system (_Deprecated_) | Boolean | | | automatic (_Deprecated_) | Boolean | | **RESPONSE CODES** | **Status** | **Description** | | --- | --- | | 200 OK | Shows if operation succeeded | | 400 Bad Request | Shows when an invalid request or the requested service is not available | ## Headers - `Accept` string - `Count` string - `ExtraFieldDescription` string ## Response `200` List Activity Types --- [API](https://skmtc.dev/forcemanager/apis/sage-sales-management-public-api-documentation-for-developer.md) · [All operations](https://skmtc.dev/forcemanager/apis/sage-sales-management-public-api-documentation-for-developer/llms.txt) · [OpenAPI document](https://skmtc.dev/forcemanager/apis/sage-sales-management-public-api-documentation-for-developer/revisions/87db17204e2f?raw)