openapi: 3.0.4 info: title: Bench AccountActivities PersonCertAttachments API description: "

Versioning

\n

\n The API is currently at version 1.0. All API endpoints (other than\n authentication) require you to specify the API version as part of the path.\n

\n\n

URL Paths

\n

\n Authentication requests should be made to /auth/signin,\n as documented below. All other API requests should be made to\n sub-paths of /rp/api/1.0/....\n

\n\n

Authentication

\n

\n API requests are authenticated using an OAuth Bearer token.\n You can get a token by authenticating your user by sending a\n POST request to /auth/signin, with \"username and \"password\"\n parameters form-encoded in the body of the request.\n\n POST /auth/signin HTTP/1.1\n Content-Type: application/x-www-form-urlencoded\n\n username=user@example.com&password=some-secret-password\n

\n

\n The response will be a JSON object including both\n \"access_token\" and \"refresh_token\" property.\n All other requests against the Bench API should include an\n authorization header: Authorization: Bearer xxxYYYzzz,\n where xxxYYYzzz is the value of \"access_token\" in the response.\n

\n For example:\n\n $ curl https://bench.gobridgit.com/auth/signin -H 'Content-Type: application/x-www-form-urlencoded' --data-urlencode 'username=someone@example.com' --data-urlencode 'password=[...snip...]'\n {\n \"access_token\": \"...snip...\",\n \"token_type\": \"Bearer\",\n \"refresh_token\": \"...snip...\"\n \"expiry\": \"2020-01-01T00:00:00.413440849Z\"\n }\n\n

\n\n

\n The refresh token can be used to generate new session by request with /auth/token endpoint:\n\n POST /auth/token HTTP/1.1\n Content-Type: application/x-www-form-urlencoded\n\n grant_type=refresh_token&refresh_token=tGzv3JOkF0XG5Qx2TlKWIA\n

\n

\n Note that once the refresh token is used, the previous access and refresh token is no longer valid.\n

\n For example:\n\n $ curl https://bench.gobridgit.com/auth/token -H 'Content-Type: application/x-www-form-urlencoded' --data-urlencode 'grant_type=refresh_token' --data-urlencode 'refresh_token=[...snip...]'\n {\n \"access_token\": \"...snip...\",\n \"token_type\": \"Bearer\",\n \"refresh_token\": \"...snip...\"\n \"expiry\": \"2020-01-01T00:00:00.413440849Z\"\n }\n

\n\n

Pagination

\n

\n Several of the API endpoints are paginated. These are denoted by\n including the offset (zero-based offset) and limit query\n parameters. For example, to request the 10 items,\n set the offset=0 to limit=10.\n
\n NOTE: the result set contains items with index of 0-9\n
\n To request the next 10 items (starting at index 10),\n set the offset=10 to limit=10\n

\n

\n Responses to paginated API endpoints return a JSON array of objects.\n If there are results beyond the page you have requested, the server\n will set a query-has-more: true header in the response.\n

\n\n

Request Encoding

\n

\n GET and DELETE requests should have parameters encoded as URL query\n parameters. Boolean values should be encoded as true and\n false, not as 1 and 0.\n

\n\n

Errors

\n

\n Errors are returned for some response codes such as 400 Bad Request in the\n following format:\n\n {\n \"errors\": [\n {\n \"errorType\": \"ValidationError\",\n \"description\": \"The value of Name must be a string with a minimum length of 1 and a maximum length of 8 and not whitespace.\",\n \"field\": \"Name\",\n \"values\": [\n null\n ]\n }\n ],\n \"title\": \"One or more validation errors occurred.\",\n \"status\": 400,\n \"instance\": \"api/v1/accounts/0/persons\",\n \"requestUid\": \"123e4567-e89b-12d3-a456-426614174000\"\n }\n

\n" version: '1.0' servers: - url: https://bench.gobridgit.com description: Bridgit Bench production security: - {} tags: - name: PersonCertAttachments paths: /rp/api/v1/accounts/{accountId}/persons/{personId}/certifications/{certId}/attachments: get: tags: - PersonCertAttachments summary: Get all attachments for a person's certification. description: '
Permissions
Person: Read
HourlyProfile: Read
PersonCerts: Read
HourlyCerts: Read
Private: Read' operationId: PersonCertAttachments_Query parameters: - name: accountId in: path description: The account ID required: true schema: type: integer format: int32 - name: personId in: path description: The person ID required: true schema: type: integer format: int64 - name: certId in: path description: The certification ID required: true schema: type: integer format: int64 - name: offset in: query description: The offset for paging response schema: maximum: 2147483647 minimum: 0 type: integer format: int32 default: 0 - name: limit in: query description: The amount of items in the response schema: maximum: 2147483647 minimum: 1 type: integer format: int32 default: 100 - name: state in: query description: The state of the attachment for filter schema: enum: - InProgress - Completed - Failed - All type: string default: Completed - name: creatorId in: query description: The ID of attachment creator for filter schema: type: integer format: int32 responses: '200': description: 'Success: List of Attachments' content: application/json: schema: type: array items: $ref: '#/components/schemas/AttachmentResponse' '401': description: Unauthorized '403': description: Forbidden post: tags: - PersonCertAttachments summary: Link an attachment to a person's certification. description: '
Permissions
Person: Read
HourlyProfile: Read
Private: Read
PersonCerts: Write
HourlyCerts: Write' operationId: PersonCertAttachments_Post parameters: - name: accountId in: path description: The account ID required: true schema: type: integer format: int32 - name: personId in: path description: The person ID required: true schema: type: integer format: int64 - name: certId in: path description: The certification ID required: true schema: type: integer format: int64 requestBody: description: The request body for the linking content: application/json: schema: $ref: '#/components/schemas/PersonCertAttachmentRequest' required: true responses: '204': description: No Content '401': description: Unauthorized '403': description: Forbidden '409': description: Conflict /rp/api/v1/accounts/{accountId}/persons/{personId}/certifications/{certId}/attachments/{id}: get: tags: - PersonCertAttachments summary: Get an attachment by ID for a person's certification. description: '
Permissions
Person: Read
HourlyProfile: Read
PersonCerts: Read
HourlyCerts: Read
Private: Read' operationId: PersonCertAttachments_Get parameters: - name: accountId in: path description: The account ID required: true schema: type: integer format: int32 - name: personId in: path description: The person ID required: true schema: type: integer format: int64 - name: certId in: path description: The certification ID required: true schema: type: integer format: int64 - name: id in: path description: The attachment ID required: true schema: type: integer format: int64 responses: '200': description: 'Success: an attachment in response' content: application/json: schema: $ref: '#/components/schemas/AttachmentResponse' '401': description: Unauthorized '403': description: Forbidden delete: tags: - PersonCertAttachments summary: Unlink an attachment from a person's certification. description: '
Permissions
Person: Read
HourlyProfile: Read
Private: Read
PersonCerts: Write
HourlyCerts: Write' operationId: PersonCertAttachments_Delete parameters: - name: accountId in: path description: The account ID required: true schema: type: integer format: int32 - name: personId in: path description: The person ID required: true schema: type: integer format: int64 - name: certId in: path description: The certification ID required: true schema: type: integer format: int64 - name: id in: path description: The attachment ID required: true schema: type: integer format: int64 responses: '204': description: No Content '401': description: Unauthorized '403': description: Forbidden components: schemas: PersonCertAttachmentRequest: type: object properties: attachmentId: type: integer format: int64 example: 1 additionalProperties: false AttachmentResponse: type: object properties: id: type: integer format: int64 example: 123 name: type: string nullable: true example: document.txt size: type: integer format: int64 example: 1024 mimeType: type: string nullable: true example: application/octet-stream isPrivate: type: boolean example: false binaryUrl: type: string nullable: true example: https://bench.gobridgit.com/bin/attachments/accounts/1/persons/1/document.txt creatorId: type: integer format: int32 example: 1 createdOn: type: string format: date-time example: '2021-01-01T00:00:00Z' state: enum: - InProgress - Completed - Failed - All type: string example: InProgress certificationIds: type: array items: type: integer format: int64 nullable: true example: - 1 additionalProperties: false securitySchemes: Bearer: type: http description: Standard Authorization header using the Bearer scheme scheme: bearer bearerFormat: JWT