9/2/2023 0 Comments Tinyurl api jsonURL hashes should be listed in "hashes" parameter and separated by comma. Second style - set same properties for many URLs. Tags prefixed with "-" will be detached from URL. Tags prefixed with "+" will be attached to URL. Tags field contains instructions for adding and removing tags. To read a group of URLs you need to pass a group of hashes in query parameter "hashes", separated with comma.įor example, lets pass a group of three hashes (a,b,c):Įach individual URL entry has "links" section listing locations of related resources. GET /urls?offset=5&limit=1&search=john&order_by=clicks "created" - Creation date, "clicks" - Total clicks, "hash" - Tiny alphabetical, "modified" - Modification date In case you are using "search" parameter, property page.total_count in response will indicate total number of matching URLs. "search" - search string (match "long_url", "note" or "hash" fields). It is also possible to paginate URLs like this Reading URLs GET /urls - get a batch (100) of most recent URLs. Otherwise, check will be performed among all domains in your account. To do so, useĭisable_long_url_duplicates=domain. URL only in your working domain ( controlled by "domain" parameter). If you are using several domains for shortening, you may check for existing long If custom_hash exists with different long URL, error 1215 will be indicated.If custom_hash exists with same long URL, existing records will be returned.If custom_hash does not exist, new record will be created.If you specify custom_hash together with "disable_long_url_duplicates" parameter, three scenarios are possible: Records from previously created links will be returned In this case, new records won't be created for existing long URLs. Passing the optional parameter "disable_long_url_duplicates": POST /urls?disable_long_url_duplicates=account Your API call doesn't specify a custom_hash it is possible to avoid duplication of long URLs by Normally our system allows creation of multiple different short links containing exactly the same long or destination URL.īut it is also possible to avoid making any new, unique short hashes if the long url had been previously submitted. In above example, one URL was successfully shortened. HTTP status code - 200 OK and top-level "error" block indicates no errors.īut inside "urls" array, some URLs may have individual error message. In both cases (successful shortening or shortening errors) "details": "That Custom hash is already in use" "message": "Short URL is not correct or existed.", Maximum length of "note" is 255 characters. Maximum length of "custom_hash" limited to 25. Maximum length of "long_url" limited to 2048. These fields depend on server configuration and may vary from server to server.Īll fields are optional except "long_url". Response contains information about different counters. "subscription_plan": "Secure Plan (1 year)", Please login to your account to manage your API keys and their permissions. Or you can restrict IP-addresses allowed to use that API key. Or you can restrict API key access to certain domains in your account. Username determines owner of the URLs that you shortening.ĪPI key determines methods that you allowed to call on different API resources.įor example, you can create read-only API-key. Use your username:api-key for user:password. They will get error 1217.Ĭustom API Keys for Branded URL Shortening Responses always encoded with "application/json".Īll date-time values in API are in UTC☐0:00. GET-parameters should be "percent-encoded". You should use POST method and set X-HTTP-Method-Override header. If you want to make PATCH (or other non POST) request with encoding other then "application/json", However "application/x-www-form-urlencoded" and "multipart/form-data" are also supported for POST requests. Recommended encoding for request's payload - "application/json". If you have problem using PATCH HTTP method, we support method override for POST calls via X-HTTP-Method-Override header. We'd love the chance to work out a custom solution. Our platform was designed to be flexible. I am relatively new to using JSON APIs in Pipelines and am having problems getting a TinyURL for a really big URL from Quickbase (I plan to use it as a QR code, so smaller is better!).Custom Domain Branded URL Shortener API Documentation Not seeing what you need? No problem, sometimes one size doesn't fit all. Subject: Need help with TinyURL API via JSON
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |