Convert query parameters from API urls to MongoDB queries
A library for simplifying encoding and decoding URL query parameters.
React Hook for managing state in URL query parameters with easy serialization.
The core `url` packaged standalone for use with Browserify.
A module to manipulate search part of URLs (querystring)
🏆 Use Ant Design Table like a Pro!
Fast, type-safe @tanstack/react-query client to work with your OpenAPI schema.
A tiny (305B) browser utility for stringifying a query Object.
Types for (de)serializing HTTP requests from both the client and server side
Convenient state management of query parameters in Next.js apps.
express middleware that normalizes incoming query param names
Append querystring params to a URL.
Returns a promise from a node-style callback function.
Drupal JSON-API params
<img alt="Third Party Capital Logo" title="Third Party Capital Logo" src="https://user-images.githubusercontent.com/12476932/229881508-f9ef68db-8ee7-4795-8de8-80a50145bbd0.png" width="150">
[](https://github.com/rudyhuynh/use-url-search-params/blob/master/License)
Common utility functions
Displays the results of a GROQ query in a View Pane
Right-to-left addon for Storybook.
All NestJS + Zod utilities you need
This package provides helpers for doing extractPlasmicQueryData() with Next.js App Router.
Retrieves values from JSON objects for data binding. Offers params, nested queries, deep queries, custom reduce/filter functions and simple boolean logic. Browserify compatible.
offers a way to query a Javascript AST to find specific patterns using a syntax somewhat similar to XPath.
use querySelector syntax to search for nodes inside of (nested) shadow roots
Rails routing constraint for api versioning in query params using the v param.
Parascope::Query class provides a way to dynamically apply scopes or ActiveRecord query methods based on passed params with a declarative and convenient API
Zen::Query class provides a way to dynamically apply scopes or ActiveRecord (or any other ORM) query methods based on passed params with a declarative and convenient API
The National Library of Medicine API, "Medlineplus Connect", can be somewhat cantankerous to work with. Query params are non sensical to end users, query format is from a bygone era, and the resulting responses often contain large amounts of superficial information. The response structures are somewhat inconsistant, and are always non intuitive. This gem simplifies querying the NLM API, and parses the responses into something more sane and structured for the average Ruby dev to use. Note that at this time, the only feature available through this gem is querying descriptions for ICD-10 codes, more API interfaces TBD.
GraphQL interface over WCC::Contentful store
Back in 2015 I was a guy automating things at my job and two scripts had a common need -- they both had to pass the same credentials to Jenkins (via query params, I guess). That common tool with a single method was a Net::HTTP wrapper -- that's where the name from. Then when the third script appeared two of them had to pass the Basic Auth. The verb POST was added and common logging format, and relatively complex retry logic. Then some website had redirects and I had to store cookies, then GZIP and API rate limits... I was not going to gemify this monster but it is now a dependency in many other gems, and since Gemfile does not support Github dependencies I have to finally gemify it.
Send SMS messages using the OpenMarket API
# Quick Start The Owner API uses the JSON format, and must be accessed over a [secure connection](https://en.wikipedia.org/wiki/HTTPS). Let’s assume that the access token provided by your account manager is “TOKEN”. Here’s how to get the list of ids of all your invoices from the first week of August with a shell script: ```bash query="end_date=2018-08-08T00%3A00%3A00%2B00%3A00&start_date=2018-08-01T00%3A00%3A00%2B00%3A00" curl -i "https://api-eu.getaround.com/owner/v1/invoices?${query}" \ -H "Authorization: Bearer TOKEN" \ -H "Accept:application/json" \ -H "Content-Type:application/json" ``` And here’s how to get the invoice with the id 12345: ```bash curl -i "https://api-eu.getaround.com/owner/v1/invoices/12345" \ -H "Authorization: Bearer TOKEN" \ -H "Accept: application/json" \ -H "Content-Type: application/json"" ``` See the [endpoints section](#tag/Invoices) of this guide for details about the response format. Dates in request params should follow the ISO 8601 standard. # Authentication All requests must be authenticated with a [bearer token header](https://tools.ietf.org/html/rfc6750#section-2.1). You token will be sent to you by your account manager. Unauthenticated requests will return a 401 status. # Pagination The page number and the number of items per page can be set with the “page” and “per_page” params. For example, this request will return the second page of invoices, and 50 invoices per page: `https://api-eu.getaround.com/owner/v1/invoices?page=2&per_page=50` Both of these params are optional. The default page size is 30 items. The Getaround Owner API follows the [RFC 8288 convention](https://datatracker.ietf.org/doc/html/rfc8288) of using the `Link` header to provide the `next` page URL. Please don't build the pagination URLs yourself. The `next` page will be missing when you are requesting the last available page. Here's an example response header from requesting the second page of invoices `https://api-eu.getaround.com/owner/v1/invoices?page=2&per_page=50` ``` Link: <https://api-eu.getaround.com/owner/v1/invoices?page=3&per_page=50>; rel="next" ``` # Throttling policy and Date range limitation We have throttling policy that prevents you to perform more than 100 requests per min from the same IP. Also, there is a limitation on the size of the range of dates given in params in some requests. All requests that need start_date and end_date, do not accept a range bigger than 30 days. # Webhooks Getaround can send webhook events that notify your application when certain events happen on your account. This is especially useful to follow the lifecycle of rentals, tracking for example bookings or cancellations. ### Setup To set up an endpoint, you need to define a route on your server for receiving events, and then <a href="mailto:owner-api@getaround.com">ask Getaround</a> to add this URL to your account. To acknowledge receipt of a event, your endpoint must: - Return a `2xx` HTTP status code. - Be a secure `https` endpoint with a valid SSL certificate. ### Testing Once Getaround has set up the endpoint, and it is properly configured as described above, a test `ping` event can be sent by clicking the button below: <form action="/docs/api/owner/fire_ping_webhook" method="post"><input type="submit" value="Send Ping Event"></form> You should receive the following JSON payload: ```json { "data": { "ping": "pong" }, "type": "ping", "occurred_at": "2019-04-18T08:30:05Z" } ``` ### Retries Webhook deliveries will be attempted for up to three days with an exponential back off. After that point the delivery will be abandoned. ### Verifying Signatures Getaround will also provide you with a secret token, which is used to create a hash signature with each payload. This hash signature is passed along with each request in the headers as `X-Drivy-Signature`. Suppose you have a basic server listening to webhooks that looks like this: ```ruby require 'sinatra' require 'json' post '/payload' do push = JSON.parse(params[:payload]) "I got some JSON: #{push.inspect}" end ``` The goal is to compute a hash using your secret token, and ensure that the hash from Getaround matches. Getaround uses an HMAC hexdigest to compute the hash, so you could change your server to look a little like this: ```ruby post '/payload' do request.body.rewind payload_body = request.body.read verify_signature(payload_body) push = JSON.parse(params[:payload]) "I got some JSON: #{push.inspect}" end def verify_signature(payload_body) signature = 'sha1=' + OpenSSL::HMAC.hexdigest(OpenSSL::Digest.new('sha1'), ENV['SECRET_TOKEN'], payload_body) return halt 500, "Signatures didn't match!" unless Rack::Utils.secure_compare(signature, request.env['HTTP_X_DRIVY_SIGNATURE']) end ``` Obviously, your language and server implementations may differ from this code. There are a couple of important things to point out, however: No matter which implementation you use, the hash signature starts with `sha1=`, using the key of your secret token and your payload body. Using a plain `==` operator is not advised. A method like secure_compare performs a "constant time" string comparison, which renders it safe from certain timing attacks against regular equality operators. ### Best Practices - **Acknowledge events immediately**. If your webhook script performs complex logic, or makes network calls, it’s possible that the script would time out before Getaround sees its complete execution. Ideally, your webhook handler code (acknowledging receipt of an event by returning a `2xx` status code) is separate of any other logic you do for that event. - **Handle duplicate events**. Webhook endpoints might occasionally receive the same event more than once. We advise you to guard against duplicated event receipts by making your event processing idempotent. One way of doing this is logging the events you’ve processed, and then not processing already-logged events. - **Do not expect events in order**. Getaround does not guarantee delivery of events in the order in which they are generated. Your endpoint should therefore handle this accordingly. We do provide an `occurred_at` timestamp for each event, though, to help reconcile ordering.
Contentful API wrapper library exposing an ActiveRecord-like interface
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.