Clarify that refreshed access tokens don't invalidate the scope of txnid (#1236)
This commit is contained in:
parent
7ab3aecf29
commit
6c6c602845
6 changed files with 14 additions and 6 deletions
|
@ -94,7 +94,7 @@ properties:
|
|||
}
|
||||
transaction_id:
|
||||
description: |
|
||||
The client-supplied transaction ID, for example, provided via
|
||||
The client-supplied [transaction ID](/client-server-api/#transaction-identifiers), for example, provided via
|
||||
`PUT /_matrix/client/v3/rooms/{roomId}/send/{eventType}/{txnId}`,
|
||||
if the client being given the event is the same one which sent it.
|
||||
type: string
|
||||
|
|
|
@ -62,7 +62,7 @@ paths:
|
|||
name: txnId
|
||||
type: string
|
||||
description: |-
|
||||
The transaction ID for this event. Clients should generate a
|
||||
The [transaction ID](/client-server-api/#transaction-identifiers) for this event. Clients should generate a
|
||||
unique ID; it will be used by the server to ensure idempotency of requests.
|
||||
required: true
|
||||
x-example: "37"
|
||||
|
|
|
@ -58,7 +58,7 @@ paths:
|
|||
name: txnId
|
||||
type: string
|
||||
description: |-
|
||||
The transaction ID for this event. Clients should generate an
|
||||
The [transaction ID](/client-server-api/#transaction-identifiers) for this event. Clients should generate an
|
||||
ID unique across requests with the same access token; it will be
|
||||
used by the server to ensure idempotency of requests.
|
||||
required: true
|
||||
|
|
|
@ -48,7 +48,7 @@ paths:
|
|||
name: txnId
|
||||
type: string
|
||||
description: |-
|
||||
The transaction ID for this event. Clients should generate an
|
||||
The [transaction ID](/client-server-api/#transaction-identifiers) for this event. Clients should generate an
|
||||
ID unique across requests with the same access token; it will be
|
||||
used by the server to ensure idempotency of requests.
|
||||
required: true
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue