Returns the latest terms of service by UUID

GET /terms/{termsId}

Fetches the latest terms for the given UUID.

Headers

Path parameters

Query parameters

  • An optional URI to redirect to in case terms of service are accepted. This parameter only has effect to the text/html version of the terms.

Responses

  • Terms found

    Hide headers attribute Show headers attribute
    • Language of the localized response properties. Is not necessarily one of the values provided by the Accept-Language request header.

    Hide response attribute Show response attribute object
    • data object
      Hide data attributes Show data attributes
      • type string

        Value is Terms.

      • id string(uuid)

        Terms ID

      • Hide attributes attributes Show attributes attributes

    A browser friendly version of the terms of service including an accept button

    A browser friendly version of the terms of service including an accept button

  • Terms found and user accepted the last version

    Hide headers attribute Show headers attribute
    • Location string(url)

      Directs the browser to go to the passed redirectUri, only if no Accept: application/vnd.api+json is send

  • 404 application/vnd.api+json

    Resource not found

    Hide response attribute Show response attribute object

    Error objects provide additional information about problems encountered while performing an operation. Errors also contain codes besides title and message which can be used for checks even if the detailed messages might change.

    * 1000: generic error * 1001: payment processing temporarily unavailable * 1002: requested amount exceeds the authorized amount of the provided token * 1003: implicit payment methods cannot be modified * 1004: payment method rejected by provider * provider:payment-method-rejected: payment method rejected by provider (identical to 1004) * rule:product-denied: Product restrictions forbid transaction, e.g., forbidden fuel type - token authorized only for Diesel but attempted to fuel Super.

    • errors array[object]
      Hide errors attributes Show errors attributes object
      • id string

        A unique identifier for this particular occurrence of the problem.

      • status string

        the HTTP status code applicable to this problem, expressed as a string value.

      • code string

        an application-specific error code, expressed as a string value.

      • title string

        A short, human-readable summary of the problem that SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization.

      • detail string

        a human-readable explanation specific to this occurrence of the problem. Like title, this field’s value can be localized.

      • source object

        An object containing references to the source of the error.

        Hide source attributes Show source attributes
        • pointer string

          A JSON Pointer [RFC6901] to the associated entity in the request document [e.g. "/data" for a primary data object, or "/data/attributes/title" for a specific attribute].

        • A string indicating which URI query parameter caused the error.

      • meta object

        a meta object containing non-standard meta-information about the error.

        Hide meta attribute Show meta attribute
  • 501 application/vnd.api+json

    Internal server error

    Hide response attribute Show response attribute object

    Error objects provide additional information about problems encountered while performing an operation. Errors also contain codes besides title and message which can be used for checks even if the detailed messages might change.

    * 1000: generic error * 1001: payment processing temporarily unavailable * 1002: requested amount exceeds the authorized amount of the provided token * 1003: implicit payment methods cannot be modified * 1004: payment method rejected by provider * provider:payment-method-rejected: payment method rejected by provider (identical to 1004) * rule:product-denied: Product restrictions forbid transaction, e.g., forbidden fuel type - token authorized only for Diesel but attempted to fuel Super.

    • errors array[object]
      Hide errors attributes Show errors attributes object
      • id string

        A unique identifier for this particular occurrence of the problem.

      • status string

        the HTTP status code applicable to this problem, expressed as a string value.

      • code string

        an application-specific error code, expressed as a string value.

      • title string

        A short, human-readable summary of the problem that SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization.

      • detail string

        a human-readable explanation specific to this occurrence of the problem. Like title, this field’s value can be localized.

      • source object

        An object containing references to the source of the error.

        Hide source attributes Show source attributes
        • pointer string

          A JSON Pointer [RFC6901] to the associated entity in the request document [e.g. "/data" for a primary data object, or "/data/attributes/title" for a specific attribute].

        • A string indicating which URI query parameter caused the error.

      • meta object

        a meta object containing non-standard meta-information about the error.

        Hide meta attribute Show meta attribute
GET /terms/{termsId}
curl \
 -X GET https://api.pace.cloud/user/2024-1/terms/2a1319c3-c136-495d-b59a-47b3246d08af \
 -H "Accept-Language: fr-CH, fr;q=0.9, en;q=0.8, de;q=0.7, *;q=0.5"
Response examples (200)
# Headers
Content-Language: en-GB

# Payload
{
  "data": {
    "type": "Terms",
    "id": "6d876562-625d-47bb-964b-25b52d6ef521",
    "attributes": {
      "version": 202004201530,
      "acceptUrl": "/api/terms/6d876562-625d-47bb-964b-25b52d6ef521/accept",
      "markdown": "# Lorem ipsum\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque volutpat congue ante non elementum. Suspendisse potenti. Nulla facilisi. Donec euismod purus at risus ultricies, quis ullamcorper nulla porttitor. Vestibulum at dui pulvinar, consequat metus ultricies, auctor libero. Nulla facilisi. Suspendisse euismod elementum diam, sit amet tempus est. Quisque congue ligula at interdum accumsan. Suspendisse porttitor erat nibh, at pellentesque sem aliquet eget. Quisque posuere libero in velit lobortis, id elementum arcu faucibus. Nullam vulputate neque turpis, vitae sollicitudin elit scelerisque vitae. Cras sit amet justo vitae est vestibulum ullamcorper. Aenean lobortis metus sed sem imperdiet vestibulum.\nNullam cursus orci non nibh sodales lobortis. **Proin eros metus, commodo nec facilisis at, sodales id ipsum. Etiam gravida ante vel leo placerat, non elementum libero placerat.** Quisque et tellus ac est accumsan venenatis egestas et risus. Proin vel tellus eu magna cursus dictum et eu erat. Quisque ultrices est a nulla accumsan, eu facilisis lorem maximus. Integer ut turpis pharetra lectus pellentesque ultricies sed eget tellus. Proin id ipsum vel ante tempor dapibus ac eget mauris. Aliquam auctor at nisl vitae rutrum.\n## 1 Ipsum Lorem\nDuis id vestibulum elit. Fusce ut neque at arcu lacinia rutrum. Mauris quis facilisis dui. Sed pharetra est mauris, vel convallis nulla vestibulum non. Mauris vulputate sit amet dolor ut convallis. Cras hendrerit in tellus nec dictum. Aliquam eleifend, lectus eu feugiat accumsan, nulla diam volutpat tellus, sed bibendum ligula nisi ac lectus. Etiam a cursus leo.\nNam lectus est, lacinia eu mi ut, hendrerit scelerisque nisl. Nunc sit amet aliquet est. Fusce euismod consequat interdum. Nunc maximus molestie sem, ac dignissim sem pellentesque id. Nulla facilisi. Nullam suscipit nisl metus, ac bibendum neque fermentum ac. Vivamus venenatis placerat elit eu dictum. Nullam at iaculis magna. Vivamus rutrum arcu quis ligula sollicitudin sagittis. In hac habitasse platea dictumst. Quisque nec finibus elit, ac rutrum elit. Ut et felis eget dolor interdum posuere.\n## 2 Lorem Lorem\nNulla fringilla aliquam tortor eu pulvinar. Maecenas posuere tortor ac sem faucibus ullamcorper. Nullam faucibus eget ipsum at mattis. Phasellus tempor euismod sem et finibus. Sed eros quam, consequat sit amet metus at, aliquam luctus diam. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Sed et erat nec tellus malesuada consequat. Maecenas odio sem, hendrerit id felis ac, tincidunt vestibulum magna. Nullam ut vulputate odio. Cras nibh mauris, condimentum nec efficitur nec, fermentum sed elit. Vivamus a nunc eget ante mattis vehicula non eu eros. Donec blandit lobortis ipsum, vitae feugiat dolor dignissim vel. Proin est nibh, efficitur in mi sit amet, placerat convallis libero. In ac purus at justo ornare euismod et vitae libero. Ut suscipit mi in tempor lobortis.\n"
    }
  }
}
Response examples (200)
<html>...</html>
Response examples (404)
{
  "errors": [
    {
      "id": "string",
      "links": {
        "about": "string"
      },
      "status": "string",
      "code": "string",
      "title": "string",
      "detail": "string",
      "source": {
        "pointer": "string",
        "parameter": "string"
      },
      "meta": {}
    }
  ]
}
Response examples (501)
{
  "errors": [
    {
      "id": "string",
      "links": {
        "about": "string"
      },
      "status": "string",
      "code": "string",
      "title": "string",
      "detail": "string",
      "source": {
        "pointer": "string",
        "parameter": "string"
      },
      "meta": {}
    }
  ]
}