SeoService_GetCountries

GET

/api/v1/seo/countries

const url = 'https://dictionary.example.invalid/api/v1/seo/countries';
const options = {method: 'GET'};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://dictionary.example.invalid/api/v1/seo/countries

Responses

200

application/json

object

countries

required

Array<object>

object

required

string

name

required

string

hotelsCount

required

string

Example

{
  "countries": [
    {
      "id": null,
      "name": null,
      "hotelsCount": null
    }
  ]
}

default

Default error response

application/json

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

object

code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32

message

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.

string

details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object

@type

The type of the serialized message.

string

key

additional properties

any

Example

{
  "code": 1,
  "message": "DEMO_VALUE",
  "details": [
    {
      "@type": null
    }
  ]
}