Travel Letters

Updates a travel letter request

Authentication

This endpoint accepts any one of the following token types:

Company-scoped access token (OAuth2AuthorizationCode) — obtained by a company manager through the Authorization Code flow or the Refresh Token flow. See Authentication for partners.
Company-scoped access token (assertion) (OAuth2CompanyManagerAssertion) — obtained through the urn:ietf:params:oauth:grant-type:jwt-bearer grant for a company manager. See OAuth Assertion.
Customer API token (CustomerAPIToken) — generated by the customer on their Integration Settings page, with the scopes they choose there. See Authorization for customers.

Scopes

Any one of the scopes in a token type's row is enough. all:write works too.

Token type	Category	Read only Scope	Write only Scope (read access implicit)
Company-scoped access token	Manage employment documents (employment_documents)	-	Manage travel letters (travel_letter:write)
Company-scoped access token (assertion)	Manage employment documents (employment_documents)	-	Manage travel letters (travel_letter:write)
Customer API token	Manage employment documents (employment_documents)	-	Manage travel letters (travel_letter:write)

put/v1/travel-letter-requests/{id}

Request

Base URL
https://gateway.remote.com
URL
https://gateway.remote.com/v1/travel-letter-requests/{id}
Auth
- OAuth 2
  Authorization code: /auth/oauth2/authorize
  Token URL: /auth/oauth2/token scopes: https://gateway.remote.com/company.manage
- or OAuth 2
  Authorization code: /auth/oauth2/authorize
  Token URL: /auth/oauth2/token scopes: travel_letter:write
- or OAuth 2
  Authorization code: /auth/oauth2/authorize
  Token URL: /auth/oauth2/token scopes: all:write
- or OAuth 2
  Client credentials
  Token URL: /auth/oauth2/token scopes: travel_letter:write
- or OAuth 2
  Client credentials
  Token URL: /auth/oauth2/token scopes: all:write
- or HTTP bearer

Path parameters

idstring required

Travel letter Request ID

Request body

Example request

{
  "employer_special_instructions": "some special instruction",
  "responsible_for_accommodation_cost": "employee",
  "responsible_for_meal_cost": "employee",
  "responsible_for_travel_cost": "employee",
  "status": "approved_by_manager"
}

Response

Success

Example response

{
  "data": {
    "travel_letter_request": {
      "additional_information": "Some additional information",
      "destination_country": {
        "alpha_2_code": "PT",
        "code": "PRT",
        "contractor_products_available": [
          "standard",
          "plus",
          "cor"
        ],
        "country_subdivisions": [
          {
            "code": "PT-06",
            "name": "Coimbra",
            "subdivision_type": "District"
          },
          {
            "code": "PT-11",
            "name": "Lisboa",
            "subdivision_type": "District"
          }
        ],
        "employment_agreement_preview_available": true,
        "eor_onboarding": true,
        "global_payroll_supported": true,
        "locked_benefits": "after_first_hire",
        "name": "Portugal",
        "region": "Europe",
        "subregion": "Southern Europe",
        "supported_json_schemas": [
          "additional_documents",
          "address_details",
          "administrative_details",
          "employment-basic-information",
          "bank_account_details",
          "contract_details",
          "emergency_contact"
        ]
      },
      "embassy_address": "some embassy address",
      "employer_approver": {
        "email": "user0@company.com",
        "id": "93aaf0b3-1d79-4d2c-8d47-3d5406727d70",
        "name": "User Name"
      },
      "employer_special_instructions": "Some special instruction",
      "id": "f4b4369e-cb29-47f0-a608-afd5e19a2102",
      "reason": "Some reason",
      "requires_travel_address": false,
      "responsible_for_accommodation_cost": "employee",
      "responsible_for_meal_cost": "employee",
      "responsible_for_travel_cost": "employee",
      "status": "pending",
      "submitted_at": "2021-07-15T18:18:17Z",
      "travel_address": "Some travel address",
      "travel_date_end": "2021-07-01",
      "travel_date_start": "2021-07-01",
      "travel_document_number": "FC123456",
      "travel_reason": "Some travel reason",
      "travel_reason_details": "Some details",
      "user": {
        "email": "user0@company.com",
        "id": "93aaf0b3-1d79-4d2c-8d47-3d5406727d70",
        "name": "User Name"
      }
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.