Queue Receive
Receives messages from a topic as competing consumers.
Messages are individually leased for the specified duration. Multiple consumers can receive different messages from the same topic concurrently. Leased messages are skipped until they are acked or their lease expires.
Request body
Example request
{
"namespace": "some_namespace",
"topic": "some_topic_name",
"consumer_group": "some_consumer_group"
}Response
Changes
Changed in 9 of the 53 revisions of this API.141926
- ●
added the new
invalid-inputenum value to theresponse property for the response statusresponse-property-enum-value-added
- ●
added the new
invalid-inputenum value to theresponse property for the response statusresponse-property-enum-value-added
- ●
added the new
invalid-inputenum value to theresponse property for the response statusresponse-property-enum-value-added
- ●
added the new
invalid-inputenum value to theresponse property for the response statusresponse-property-enum-value-added
- ●
added the new
operation-errorenum value to theresponse property for the response statusresponse-property-enum-value-added
- ●
added the new
operation-errorenum value to theresponse property for the response statusresponse-property-enum-value-added
- ●
added the new
operation-errorenum value to theresponse property for the response statusresponse-property-enum-value-added
- ●
added the new
operation-errorenum value to theresponse property for the response statusresponse-property-enum-value-added
- ●
added the new
server-errorenum value to theresponse property for the response statusresponse-property-enum-value-added
- ●
added the new
server-errorenum value to theresponse property for the response statusresponse-property-enum-value-added
- ●
added the new
server-errorenum value to theresponse property for the response statusresponse-property-enum-value-added
- ●
added the new
server-errorenum value to theresponse property for the response statusresponse-property-enum-value-added
- ○
removed the
invalid_inputenum value from theresponse property for the response statusresponse-property-enum-value-removed
- ○
removed the
invalid_inputenum value from theresponse property for the response statusresponse-property-enum-value-removed
- ○
removed the
invalid_inputenum value from theresponse property for the response statusresponse-property-enum-value-removed
- ○
removed the
invalid_inputenum value from theresponse property for the response statusresponse-property-enum-value-removed
- ○
removed the
operation_errorenum value from theresponse property for the response statusresponse-property-enum-value-removed
- ○
removed the
operation_errorenum value from theresponse property for the response statusresponse-property-enum-value-removed
- ○
removed the
operation_errorenum value from theresponse property for the response statusresponse-property-enum-value-removed
- ○
removed the
operation_errorenum value from theresponse property for the response statusresponse-property-enum-value-removed
- ○
removed the
server_errorenum value from theresponse property for the response statusresponse-property-enum-value-removed
- ○
removed the
server_errorenum value from theresponse property for the response statusresponse-property-enum-value-removed
- ○
removed the
server_errorenum value from theresponse property for the response statusresponse-property-enum-value-removed
- ○
removed the
server_errorenum value from theresponse property for the response statusresponse-property-enum-value-removed
- ●
- ○
added the required property
to the response with the statusresponse-required-property-added
- ○
added the required property
to the response with the statusresponse-required-property-added
- ○
added the required property
to the response with the statusresponse-required-property-added
- ○
added the required property
to the response with the statusresponse-required-property-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ▲
the
response's property type changed fromarraytostringfor statusresponse-property-type-changed
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the required property
to the response with the statusresponse-required-property-added
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ▲
the
request property's minLength was increased from0to1request-property-min-length-increased
- ▲
- ▲
added the pattern
^[a-zA-Z0-9\-/_.=+]+$to the request propertyrequest-property-pattern-added
- ●
the
request property's maxLength was set to256request-property-max-length-set
- ▲
- ▲
the
//response's property type changed fromstringtointeger, and format fromdate-timetouint64for statusresponse-property-type-changed
- ▲
the
//response's property type changed fromstringtointeger, and format fromdate-timetouint64for statusresponse-property-type-changed
- ▲
- ○
the response property
//became required for the statusresponse-property-became-required
- ○
the
response's property default value{}was removed for the statusresponse-property-default-value-removed
- ○
- ●
the
request property's min was set to0.00request-property-min-set
- ●
the
request property's min was set to0.00request-property-min-set
- ●
- ▲
the response property
//became optional for the statusresponse-property-became-optional
- ▲
the
response's property type changed fromstringtoarrayfor statusresponse-property-type-changed
- ▲
the
//response's property type changed fromintegertostring, and format fromuint64todate-timefor statusresponse-property-type-changed
- ▲
the
//response's property type changed fromintegertostring, and format fromuint64todate-timefor statusresponse-property-type-changed
- ▲
removed the required property
from the response with the statusresponse-required-property-removed
- ▲
removed the required property
from the response with the statusresponse-required-property-removed
- ▲
removed the required property
from the response with the statusresponse-required-property-removed
- ▲
removed the required property
from the response with the statusresponse-required-property-removed
- ▲
removed the required property
from the response with the statusresponse-required-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ○
the
request property's minLength was decreased from1to0request-property-min-length-decreased
- ○
removed the pattern
^[a-zA-Z0-9\-/_.=+]+$from the request propertyrequest-property-pattern-removed
- ○
the
response's property default value{}was added for the statusresponse-property-default-value-added
This revision also has 35 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲