openapi: 3.2.0 info: title: Reference Eng Users API version: '2.0' summary: API description: "Vessel's APIs requires an access token to be used together with your Vessel API token. Ensure the following headers are provided when making API calls:\n\nKey | Value | Description\n---------|----------|----------\n vessel-api-token | `` | The API token provided by us\n \nAdditionally, in the query or body parameters of each request depending on whether it is a GET or POST, make sure to include the `accessToken` for the connection you want to access." servers: - url: https://api.vessel.land security: - VesselAPIToken: [] tags: - name: engUsers paths: /engagement/users: parameters: [] get: summary: Get All Users tags: - engUsers responses: '200': description: OK content: application/json: schema: title: responseBody type: object properties: users: type: array items: $ref: '#/components/schemas/EngUser' nextPageCursor: type: string examples: example-1: value: users: - id: 34f5b4b0b6b650c981a174b02753c390 firstName: Micheal lastName: Scott email: micheal@dundermifflin.com createdTime: '2019-08-24T14:15:22Z' modifiedTime: '2019-08-24T14:15:22Z' associations: taskIds: - 2322707bbc41577d9806400e2daa25de actionIds: - 006b4db16b6b50c981a174b02753c390 additional: {} nextPageCursor: string operationId: get-all-engagement-users parameters: - $ref: '#/components/parameters/accessToken' - $ref: '#/components/parameters/cursor' - $ref: '#/components/parameters/limit' - $ref: '#/components/parameters/allFields' description: Retrieve all Users /engagement/user: parameters: [] get: summary: Get User tags: - engUsers responses: '200': description: OK content: application/json: schema: title: responseBody type: object properties: user: $ref: '#/components/schemas/EngUser' examples: example-1: value: user: id: 34f5b4b0b6b650c981a174b02753c390 firstName: Micheal lastName: Scott email: micheal@dundermifflin.com createdTime: '2019-08-24T14:15:22Z' modifiedTime: '2019-08-24T14:15:22Z' associations: taskIds: - 2322707bbc41577d9806400e2daa25de actionIds: - 006b4db16b6b50c981a174b02753c390 additional: {} operationId: get-one-engagement-user parameters: - $ref: '#/components/parameters/accessToken' - $ref: '#/components/parameters/id' - $ref: '#/components/parameters/allFields' description: Retrieve a single User by Id components: schemas: EngUser: title: User type: object description: Users of the connected Engagement platform. These are *not* the contacts or leads, but rather the user accounts from the connected Engagement Platform. examples: - id: 56f653659ea9524b9e0fb0ba67e6f8a0 firstName: Micheal lastName: Scott email: micheal@dundermifflin.com createdTime: '2019-08-24T14:15:22Z' modifiedTime: '2019-08-24T14:15:22Z' associations: taskIds: - 2322707bbc41577d9806400e2daa25de actionIds: - 006b4db16b6b50c981a174b02753c390 additional: {} properties: id: type: string description: Id of the object in the connected Engagement Platform. firstName: type: string lastName: type: string email: format: email type: string createdTime: type: string description: The timestamp that the user was created modifiedTime: type: string description: Not supported by Apollo. The timestamp the user was last modified. associations: type: object required: - taskIds - actionIds properties: taskIds: type: array items: type: string actionIds: type: array items: type: string additional: type: object description: Returned when `allFields` is set in the query params. Includes all data, untransformed, we received from the downstream Engagement Platform required: - id - createdTime - modifiedTime - associations parameters: cursor: name: cursor in: query description: The cursor to use for pagination schema: type: string id: name: id in: query description: The id of the object to retrieve required: true schema: type: string accessToken: name: accessToken in: query description: The token for the customer's account. This was generated when they connected their account. required: true schema: type: string allFields: name: allFields in: query description: Returns all fields including non-unifiable and custom fields under the "additional" property in the response schema: type: boolean limit: name: limit in: query description: The number of records to return per page. schema: type: number securitySchemes: VesselAPIToken: name: vessel-api-token type: apiKey in: header x-speakeasy-name-override: - operationId: post-* methodNameOverride: create - operationId: put-* methodNameOverride: update - operationId: delete-* methodNameOverride: delete - operationId: get-one-* methodNameOverride: find - operationId: get-all-* methodNameOverride: list - operationId: get-details-* methodNameOverride: details - operationId: get-batch-* methodNameOverride: batch - operationId: search-* methodNameOverride: search