question

blueprintChris avatar image
blueprintChris asked ·

No Slot ID or Synonyms in JSON for IntentRequest

According to Amazon's Documentation on Standard Request Types, a typical IntentRequest should look like the following:

{
  "type": "IntentRequest",
  "requestId": "string",
  "timestamp": "string",
  "dialogState": "string",
  "locale": "string",
  "intent": {
    "name": "string",
    "confirmationStatus": "string",
    "slots": {
      "SlotName": {
        "name": "string",
        "value": "string",
        "confirmationStatus": "string",
        "resolutions": {
          "resolutionsPerAuthority": [
            {
              "authority": "string",
              "status": {
                "code": "string"
              },
              "values": [
                {
                  "value": {
                    "name": "string",
                    "id": "string"
                  }
                }
              ]
            }
          ]
        }
      }
    }
  }
}

But, as you can see in the following example, mine looks like this (note the lack of slot ID and synonyms):

    "type": "IntentRequest",
    "requestId": "some-id",
    "intent": {
      "name": "SomeIntent",
      "slots": {
        "entity": {
          "name": "entity",
          "value": "entityValue"
        }
      }
    }

I have the skill both in the UK and the US and both produce the same request schema. Anyone found a solution to this?

Why would Amazon document it like one way but have it work another?

Thanks

alexa skills kitintentsslotsdocumentationschema
10 |2000 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

0 Answers