How is an entry considered a match?īefore we explain how we identify matches to your search terms we have toĮxplain how these terms are transformed before they are sent to the searchĮngine. Which content is looked up during a global full-text search?Īll text (both regular and rich text) and symbol fields in all the locales in yourĮnvironment will be looked up when doing a global full-text search. Restrictions will apply to the other types. Remainder of this section we will refer to entries but the same principles and Terms in any of their text and symbol fields.įull-text search can be used to find entries, assets or content types. With it you can find all the content resources which match your search For cases like these full-text search is the perfect tool for (for entries) or on which field those terms can be, so you can't use any of theįield filters. Some particular words (search terms) but you don't know from which content type There are cases where you want to find all the content resources which contain You have available two flavours of full-text search:įield scoped, described in the section full-text search on a field If you provide an invalid property path, e.g fields.doesNotExist, Contentful returns a 400 Bad request containing the invalid property path. If you use the select operator on an Entry with linked fields, only the content linked to a field you select will be returned. If you want to select a property for a specific locale, you need to combine the select and locale operators, e.g /assets/?select=fields.productName&locale=en-US. It can only select properties to a depth of 2. It is only applicable for collections of Entries and Assets, and with an Entry you must provide the content_type query parameter. The select operator has some restrictions: For example, a Space resource will have a sys.type and sys.id: /entries/?select=fields&content_type=2PqfXUJwE8qSYKuM0U6w8M Note: None of the sys fields are editable and you can only specify the sys.id in the creation of an item (If it's not a *space_).Ĭontentful defines the sys.id property for every resource that is not a collection. The exact metadata available depends on the resource type, but at minimum it defines the sys.type property.
Meaning: wait 1 second before making more requests.Įvery resource returned by the Content Delivery API will have a sys property, which is an object containing system managed metadata. The current rate limit for a client is the default 55 per second.Ĭlient: 85 uncached requests in 1 second HTTP/1.1 429
The value of this header is an integer specifying the time before the limit resets and another request will be accepted.Īs the client is rate-limited per second, the header will return 1, which means the next second.
When a client gets rate limited, the API responds with the 429 Too Many Requests HTTP status codeĪnd sets the X-Contentful-RateLimit-Reset header that tells the client when it can make its next single request. Higher rate limits may apply depending on your current plan. For requests that do hit the Content Delivery API enforces the request doesn't count towards your rate limitĪnd you can make an unlimited amount of cache hits. There are no limits enforced on requests that hit our CDN cache, i.e. API Rate limits specify the number of requests a client can make to Contentful APIs in a specific time frame.Įvery request counts against a per-second rate limit.
0 kommentar(er)
