> ## Documentation Index > Fetch the complete documentation index at: https://docs.sterndesk.com/llms.txt > Use this file to discover all available pages before exploring further. # ListSTCWCertificateExtractionsForCrewProfile > list stcw certificate extractions for crew profile ## OpenAPI ````yaml https://edge.test.sterndesk.com/api/openapi.yaml post /rpc/rpc.v1.OrganizationService/ListSTCWCertificateExtractionsForCrewProfile openapi: 3.1.0 info: title: Sterndesk API version: 1.0.0 description: > HTTP/JSON access to the Sterndesk data available to your account. Every Sterndesk operation is a Connect RPC: send `POST ` with a JSON body and the `Connect-Protocol-Version: 1` header. Authenticate with a personal API key (Settings → My account → API keys) using `Authorization: Bearer `. A key reads everything documented here. The one write operation is uploading candidate documents, which needs a key carrying the `sterndesk:documents:write` permission; permissions are chosen when the key is created and are never added to an existing key. Every other write operation is rejected. ## Uploading candidate documents An upload is a batch of documents, the same batch a recruiter hands to Sterndesk from the dashboard. It may hold the documents of one candidate or of several people: Sterndesk groups them by identity and creates one candidate per person. Sending them takes two calls. 1. `POST /rpc/rpc.v1.OrganizationService/CreateManualUpload` creates the upload and returns a signed, time-limited instruction: `upload_url`, `params`, `signature` and `expires_at`, together with the limits the upload must satisfy. 2. `POST /assemblies` sends the files to Transloadit, the upload processor, as `multipart/form-data`, with `params` and `signature` as form fields. Send both verbatim: the signature covers those exact bytes, so pretty-printing `params`, reordering its keys, or parsing and re-encoding it invalidates the signature. The files go straight to Transloadit and never pass through Sterndesk. Processing then continues asynchronously, exactly as it does for a dashboard upload. `POST /rpc/rpc.v1.OrganizationService/ListManualUploads` reports the progress of the upload created in step 1. servers: - url: https://edge.sterndesk.com security: - apiKey: [] tags: - name: rpc.v1.OrganizationService description: Organization service RPC for organization method. - name: rpc.v1.RootService description: RootService provides top-level RPCs. paths: /rpc/rpc.v1.OrganizationService/ListSTCWCertificateExtractionsForCrewProfile: post: tags: - rpc.v1.OrganizationService summary: ListSTCWCertificateExtractionsForCrewProfile description: list stcw certificate extractions for crew profile operationId: rpc.v1.OrganizationService.ListSTCWCertificateExtractionsForCrewProfile parameters: - name: Connect-Protocol-Version in: header description: Define the version of the Connect protocol required: true schema: $ref: '#/components/schemas/connect-protocol-version' example: 1 - name: Connect-Timeout-Ms in: header description: Define the timeout, in ms schema: $ref: '#/components/schemas/connect-timeout-header' example: 1000 requestBody: content: application/json: schema: $ref: >- #/components/schemas/rpc.v1.ListSTCWCertificateExtractionsForCrewProfileRequest required: true responses: '200': description: Success content: application/json: schema: $ref: >- #/components/schemas/rpc.v1.ListSTCWCertificateExtractionsForCrewProfileResponse default: description: Error content: application/json: schema: $ref: '#/components/schemas/connect.error' components: schemas: connect-protocol-version: type: number examples: - 1 title: Connect-Protocol-Version description: Define the version of the Connect protocol const: 1 connect-timeout-header: type: number examples: - 1000 title: Connect-Timeout-Ms description: Define the timeout, in ms rpc.v1.ListSTCWCertificateExtractionsForCrewProfileRequest: type: object properties: crewProfileId: type: string title: crew_profile_id format: uuid description: ID of the crew profile deduplicated: type: - boolean - 'null' title: deduplicated description: enable removing document duplicates title: ListSTCWCertificateExtractionsForCrewProfileRequest additionalProperties: false description: Request for listing STCW certificate extractions for a crew profile. rpc.v1.ListSTCWCertificateExtractionsForCrewProfileResponse: type: object properties: items: type: array items: $ref: >- #/components/schemas/rpc.v1.ListSTCWCertificateExtractionsForCrewProfileResponse.Item title: items description: items title: ListSTCWCertificateExtractionsForCrewProfileResponse additionalProperties: false description: Response for listing STCW certificate extractions for a crew profile. connect.error: type: object properties: code: type: string examples: - not_found enum: - canceled - unknown - invalid_argument - deadline_exceeded - not_found - already_exists - permission_denied - resource_exhausted - failed_precondition - aborted - out_of_range - unimplemented - internal - unavailable - data_loss - unauthenticated description: >- The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code]. message: type: string description: >- A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client. details: type: array items: $ref: '#/components/schemas/connect.error_details.Any' description: >- A list of messages that carry the error details. There is no limit on the number of messages. title: Connect Error additionalProperties: true description: >- Error type returned by Connect: https://connectrpc.com/docs/go/errors/#http-representation rpc.v1.ListSTCWCertificateExtractionsForCrewProfileResponse.Item: type: object properties: documentSetId: type: string title: document_set_id description: ID of the document set the extraction is from documentId: type: string title: document_id description: ID of the document the extraction is from pageIndex: type: string title: page_index format: int64 description: Index of the page the extraction is from kind: allOf: - $ref: '#/components/schemas/rpc.v1.DocumentExtractionKind' title: kind description: Kind of extraction kindSequence: type: string title: kind_sequence format: int64 description: Sequence number if multiple of the same kind reasoning: type: array items: type: string title: reasoning description: Reasoning from the extraction snippet: type: string title: snippet description: Snippet of the text from the document createdAt: allOf: - $ref: '#/components/schemas/google.protobuf.Timestamp' title: created_at description: When the extraction was created updatedAt: allOf: - $ref: '#/components/schemas/google.protobuf.Timestamp' title: updated_at description: When the extraction was updated certificateId: type: string title: certificate_id description: Certificate-specific fields assessedAt: allOf: - $ref: '#/components/schemas/google.protobuf.Timestamp' title: assessed_at description: when it is assessed expiresAt: allOf: - $ref: '#/components/schemas/google.protobuf.Timestamp' title: expires_at description: expiry date doesNotExpire: type: boolean title: does_not_expire description: if it odes not expire name: type: string title: name description: name of the cert isEndorsed: type: boolean title: is_endorsed description: STCW certificate-specific fields countryOfIssueIso31661: type: - string - 'null' title: country_of_issue_iso3166_1 description: country it was issued in codeReasoning: type: array items: type: string title: code_reasoning description: reasoning about the code copCode: type: - string - 'null' title: cop_code description: certificate of proficency cocCode: type: - string - 'null' title: coc_code description: certificate of competency title: Item additionalProperties: false description: item ofo the list connect.error_details.Any: type: object properties: type: type: string description: >- A URL that acts as a globally unique identifier for the type of the serialized message. For example: `type.googleapis.com/google.rpc.ErrorInfo`. value: type: string format: binary description: >- The Protobuf message, serialized as bytes and base64-encoded. The specific message type is identified by the `type` field. debug: type: object title: Debug additionalProperties: true description: >- Deserialized error detail payload. The 'type' field indicates the schema. This field is for easier debugging and should not be relied upon for application logic. additionalProperties: true description: >- Contains an arbitrary serialized message along with a @type that describes the type of the serialized message, with an additional debug field for ConnectRPC error details. rpc.v1.DocumentExtractionKind: type: string title: DocumentExtractionKind enum: - DOCUMENT_EXTRACTION_KIND_UNSPECIFIED - DOCUMENT_EXTRACTION_KIND_DATE_OF_BIRTH - DOCUMENT_EXTRACTION_KIND_NATIONALITY - DOCUMENT_EXTRACTION_KIND_COUNTRY_OF_RESIDENCE - DOCUMENT_EXTRACTION_KIND_ON_LAND_WORK_EXPERIENCE - DOCUMENT_EXTRACTION_KIND_AT_SEA_WORK_EXPERIENCE - DOCUMENT_EXTRACTION_KIND_CERTIFICATE - DOCUMENT_EXTRACTION_KIND_STCW_CERTIFICATE - DOCUMENT_EXTRACTION_KIND_FACE_IMAGE description: Different kinds of information that can be extracted from a document google.protobuf.Timestamp: type: string examples: - '2023-01-15T01:30:15.01Z' - '2024-12-25T12:00:00Z' format: date-time description: >- A point in time in RFC 3339 format, with up to nanosecond precision. Output uses UTC (`Z`); input may use an offset from UTC. securitySchemes: apiKey: type: http scheme: bearer description: 'Personal API key, sent as `Authorization: Bearer `.' ````