getHPinfo - what's that site running?

Home IP-Whois similar lookup

docs.raisedonors.com

last data update: 31.05.2022 16:21:34

The Domain docs.raisedonors.com is hosted in United States and is using nginx as serversoftware.

Keywords of the webseite

this site has no keywords

Advertisement

Geo-Location

Geo-Informations

Latitude 37.7510
Longtitude -97.8220
Country United States

Alexa ranking and web history of docs.raisedonors.com

Show Alexa siteinfo

How did docs.raisedonors.com look in the past via web.archive.org

General domaininformations

  
First seen 31.05.2022 16:20:10
Reg-Created 01.01.1978
Reg-Expire 01.01.1978
Domainnamedocs.raisedonors.com
Root-Domainraisedonors.com (more)
Serversoftware nginx (more)
external Links on landingpage 0
Description The RaiseDonors API uses the [REST](http://en.wikipedia.org/wiki/Representational_State_Transfer) architectural style. Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which are understood by off-the-shelf HTTP clients. We support [cross-origin resource sharing](http://en.wikipedia.org/wiki/Cross-origin_resource_sharing), allowing you to interact securely with our API from a client-side web application. [JSON](http://www.json.org/) is returned by all API responses, including errors. There is no test mode with our API. Only read or read/write keys that can be managed in your account. We strongly encourage you to download [Postman](http://getpostman.com/downloads) and use our collection to get started. You can download the complete API collection to run and mock in Postman. [](https://app.getpostman.com/run-collection/9a3ef4034c5848ac5105) [![](https://run.pstmn.io/button.svg)](https://app.getpostman.com/run-collection/9a3ef4034c5848ac51 05) # Setup To get started consuming the API requires the setup one or more API applications in RaiseDonors and access for that application. It is possible to create API applications that only have read access to the data while others have Read/Write access. Once logged in to RaiseDonors, go to the API menu section and click on applications. This is where the applications can be viewed and managed. An application is a container that will hold multiple API license keys for read/write consumption of the API. It allows the consumer to be secure in the API calls that are made. It also allows RaiseDonors to keep metrics on the applications that are hitting the API -- which is particularly powerful in case malicious activity occurs. API applications are created to organize the different applications that the organization is developing that will be consuming the API. ![](http://raisedonors.s3.amazonaws.com/images/rd-api-documentation-1.png) 1. In the menu is a section for the API. Here you will find all the navigation concerning the API. 2. The organization key is important. It is necessary for the RaiseDonors API to identify the organization the request is for. The organization key will be passed with each request in the headers with the header name "X-OrganizationKey" 3. The list of applications that have been created by the organization. Clicking on an application name will display the details about that application. 4. To create a new application, click the "+New Application" button. ## Create New Application Creating a new API application consists of a title, a description and an indicator for if the API application is Active. It is possible to disable an application without deleting it. ![](http://raisedonors.s3.amazonaws.com/images/rd-api-documentation-2.png) 1. Name each API application a unique name that quickly describes the application that is being built that will consume the API. 2. Toggle whether the API application is active or not. If the API application is active, then the API keys that make up that application will be able to be used for API requests. 3. The description allows for a more robust explanation of the purpose of the API application. 4. Click the "Save application" button when all information is filled out. *When an API application is not active, the API license keys for that application will not be able to be used for API requests.* ## Manage API Application When an API application is created and either (1) needs to be viewed or (2) license keys need to be managed for the API application: clicking the name of the API application from the "Applications" screen will show the details of the API application. Managing the API application will allow for the editing of the details of the application, managing the API license keys for that application, and the ability to delete the API application. ![](http://raisedonors.s3.amazonaws.com/images/rd-api-documentation-3.png) 1. Edit the details of the API application (Name, description and whether it is active) by clicking "Edit Details". 1. The list of application license keys are shown here. The license key is necessary for all API requests. 1. New license keys can be created by clicking "+ New License Key" 1. Delete an API application by clicking "Delete". *When an application is deleted, all license keys become revoked. At that point no license keys for that application will be able to be used for API requests.* ## API License Keys API license keys are what tell the API what data can be consumed and in what fashion. Creating multiple API license keys is beneficial as the license key itself can be revoked. Allowing for some API keys to be read only while some having the ability to write from the API will narrow the scope of each API license key. ![](http://raisedonors.s3.amazonaws.com/images/rd-api-documentation-4.png) 1. Name the license key something unique that easily identifies the purpose of the API license key. 1. Identify if the license key is to be used for only reading data or if the license key has the ability to write data to the API. 1. Save the API key by clicking "Save API key". 1. When editing the license key, there is the ability to revoke the license key. Revoke the license key by clicking "Revoke API key". # Authentication All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). Calls made over plain HTTP will fail. API requests without authentication will also fail. Passing appropriate headers for the API call is important in order to receive good responses back from the API. ## Headers ``` Content-Type: application/json X-OrganizationKey: Authorization: Basic ``` | Key | Value | | --- | --- | | X-OrganizationKey | The organization key. It can be found on the "Applications" screen within RaiseDonors. Replace with the organization key found in RaiseDonors. | | Authorization | Header will be set to basic. Replace with the API license key from one of the API applications created in RaiseDonors. | # Pagination All top-level GET API resources have support for bulk fetches. For instance, you can list donors, funds, donations, and campaigns. These GET API methods share a common structure, taking these two parameters: page, pageSize. | Parameter | Type | Description | | --- | --- | --- | | page | Integer | The incremental page number for the request. If this value is not provided, a default "1" is used. | | pageSize | Integer | The number of records to return at a time from the requisition. If this value is not provided, a default "20" is used. There is an upper limit enforced at the server set to 200. | If your account had 250 donors, and you wanted to retrieve the first 50 donors, you could use a call similar to, > [https://api.raisedonors.com/v1/donors?page=1&pageSize=50](https://api.raisedonors.com/v1/donor s?page=1&pageSize=50) If you wanted to view the donors from 200-210, you could use a call similar to > [https://api.raisedonors.com/v1/donors?page=20&pageSize=10](https://api.raisedonors.com/v1/dono rs?page=20&pageSize=10) When pagination is in use, the response header will contain helpful information about the total number of records available. Look at the "x-pagination" element below. Response Headers: ``` content-encoding:gzip content-type:application/json; charset=utf-8 date:Wed, 20 Sep 2017 13:41:15 GMT server:cloudflare-nginx status:200 x-pagination:{"totalCount":50,"totalPages":3,"prevPageLink":"htt ps://api.raisedonors.com/v1/donations?createdAfter=2017-1-1&createdBefore=2017-12-31&page=3 &pageSize=20?page=2&pageSize=20","nextPageLink":""} x-powered-by:ASP.NET ``` The table below outlines the information RaiseDonors will include with the x-pagination element in the response header. | Parameter | Type | Description | | --- | --- | --- | | totalCount | Integer | The total number of records in the database. | | totalPages | Integer | The total number of pages available using the pageSize specified. | | prevPageLink | String | Url that can be called to retrieve the previous page, if one exits. | | nextPageLink | String | Url that can be called to retrieve the next page, if one exists. | # Throttling Our goal with throttling (aka API rate limiting) is that any API application under normal circumstances will never be throttled. Throttling is in place to protect API partners and RaiseDonors from A) attacks and B) programming errors in an app that lead to high levels of API calls that never end. While throttling exists, default limits are more than sufficient for most API usage. To increase your throttling levels please contact [[email protected]](mailto:[email protected]). Throttling is not applicable to public endpoints. Public is defined by any endpoint successfully connecting without authentication. (such as \~/public/widgets/*) The following list is comprehensive meaning each rule is applicable and once a rule is broken, your request will be throttled. All requests are tallied cummuliatevely together. s = second. m = minute. h = hour. d = day. | Period | Limit | Description | | --- | --- | --- | | 1m | 100 | 100 requests per minute. | | 1h | 1,000 | 1,000 requests per hour. | | 1d | 4,000 | 4,000 requests per day. | For example, if your requests are coming in at 50 per minute consistently, after 20 minutes (50 requests/min for 20 mintues = 1,000 requess) your requests will pass the limit of 1,000 per hour. Each additional request will be blocked. The header response will provide information on how long the block is in place for. You are allowed a total of 4,000 requests per day. Each request will include the following header elements. ``` X-Rate-Limit-Limit: the rate limit period (eg. 1m, 12h, 1d) X-Rate-Limit-Remaining: number of request remaining X-Rate-Limit-Reset: UTC date time (ISO 8601) when the limits resets ``` If the request gets blocked then the client receives a text response like this: ``` { "message": "Rate limit exceeded quota.", "details": "Maximum allowed: 2 per 1m. Please try again in 46 second(s)." } ``` And the header will contain an element, "Retry After" - which indicates the number of seconds to wait before trying agin. # Optional Parameters Some api end-points have optional parameters that can be used for various types of searching. If a end-point supports one or more of these optional parameters, it will be documented with the specific end-point object below. | Name | Type | Description | | --- | --- | --- | | createdAfter | Date (yyyy-mm-dd) | A date to start the search for objects (that have a dateCreated property). It gets objects where the created date is greater than or equal to this value. | | createdBefore | Date (yyyy-mm-dd) | A date to end the search for objects (that have a dateCreated property). It gets objects where the created date is less than or equal to this value. | | includeTestTransactions | Boolean (True/False) | A boolean to indicate if the endpoint should return both live and test transactions. The default if not provided is false. | | includeDetails | Boolean (True/False) | A boolean to indicate if the endpoint should return nested data for the object. For example, when a donor is retrieved, by default addresses are not included. Setting this value to true, the nested objects (address) will be included. The default if not provided is false. | | searchString | String | A provided value used to search key properties of objects in RaiseDonors. | | code | String | A user defined value for ‘code‘ used in some objects in RaiseDonors. | | isActiveOnly | Boolean | Determines if Active vs InActive records are returned. | | modifiedOnOrAfter | Date (yyyy-mm-dd) | A date to start the search for objects (that have a lastModified property). It gets objects where the last modified date is greater than or equal to this value. | Various end points below can use these optional parameters. Here are a few examples of how to use the optional parameters. If you desired to retrieve any donations created in the month of July, you could use a call similar to, > [https://api.raisedonors.com/v1/donations?createdAfter=2017-7-1&createdBefore=2017-7-31](https: //api.raisedonors.com/v1/donations?createdAfter=2017-7-1&createdBefore=2017-7-31) If you desired to retrieve test donations along with real donations, you could use a call similar to, > [https://api.raisedonors.com/v1/donations?includeTestTransactions=true](https://api.raisedonors.com /v1/donations?includeTestTransactions=true) If you desired to retrieve donors with all objects expanded, you could use a call similar to, > [https://api.raisedonors.com/v1/donors?includeDetails=true](https://api.raisedonors.com/v1/donors?i ncludeDetails=true) # Static Objects Some objects in RaiseDonors have fixed values for names (Enumerators). Below is a list of the Enumerators in RaiseDonors. ## Card Brand | Name | Value | | --- | --- | | American Express | 1 | | MasterCard | 2 | | Visa | 3 | | Discover | 4 | | Other | 5 | ## Payment Tender Type | Name | Value | | --- | --- | | None | 0 | | Credit Card | 1 | | E-Check | 2 | | Cash | 4 | | Check | 5 | | Stock | 6 | | Other | 7 | | Plaid | 8 | | PayPal / Venmo | 9 | | Free | 10 | ## Donation Status | Name | Value | | --- | --- | | Approved | 1 | | Declined | 2 | | Voided | 3 | | Refunded | 4 | | Error | 5 | ## Recurring Schedule Status | Name | Value | | --- | --- | | Active | 1 | | Cancelled | 2 | | Expired | 3 | | Suspended | 4 | | Terminated | 5 | | Error | 6 | ## Recurring Frequencies | Name | Value | | --- | --- | | Weekly | 52 | | Monthly | 12 | | Quarterly | 4 | | Biannually | 2 | | Annually | 1 | | Other | 100 | ## Address Type | Name | Value | | --- | --- | | Shipping | 1 | | Billing | 2 | | Technical | 3 | | Contact | 4 | ## Webhook Subscription EventType | Name | Value | | --- | --- | | Donation.Created | 1 | | Donation.Edited | 2 | | Donor.Created | 3 | | Donor.Edited | 4 | | Donor.Deleted | 5 | | Schedule.Created | 6 | | Schedule.Edited | 7 | | Schedule.Deleted | 8 | | Fund.Created | 9 | | Fund.Edited | 10 | | Fund.Deleted | 11 | | Campaign.Created | 12 | | Campaign.Edited | 13 | | Campaign.Deleted | 14 | | Product.Created | 16 | | Product.Edited | 17 | | Product.Deleted | 18 | ## Webhook Subscription Status | Name | Value | | --- | --- | | Active | 1 | | Paused | 2 | ## Webhook Subscription Format | Name | Value | | --- | --- | | JSON | 1 | | XML | 2 | ## AmountDisplayType | Name | Value | | --- | --- | | TextBox | 1 | | PrePopulatedAmount | 2 | | SuggestedAmounts | 3 | ## FrequencyOptions | Name | Value | | --- | --- | | Recurring | 1 | | OneTime | 2 | | Either | 3 | ## PaymentTenderSupported | Name | Value | | --- | --- | | CC | 1 | | ACH | 2 | | CcAndAch | 3 | ## FundDisplayType | Name | Value | | --- | --- | | Single | 0 | | Multiple_TableLayout | 1 | | Fund_ShoppingCart | 2 | # (Empty) Requests To help facilitate what JSON payloads need to include when creating objects thru the RaiseDonors API, for each object type you will find a "Object (Empty)" end point URL. Hitting this URL will return a skeleton JSON payload which you can then use for POST/PUT requests. # Sending POSTS When using the RaiseDonors API to create objects, the body of the request must be formatted as valid JSON. Send the body as raw, plain text JSON. # Date and Time Zone information All date and time data sent or received to/from RaiseDonors‘ API should and will be in UTC (Universal) time. The format should be MM/DD/YYYY HH:MM:SS AM/PM. Example, for Christmas day, 3pm, 12/25/2019 03:00:00 PM # Versioning When we make backwards-incompatible changes to the API, we release new, ‘versioned‘ versions. The current version is **‘v1‘**. Except for the Campaign endpoint, which has a **‘v2‘** version. When possible, always use the highest version, which will be the most current. # Errors RaiseDonors uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the `2xx` range indicate success. Codes in the `4xx` range indicate an error that failed given the information provided (e.g., a required parameter was omitted). Codes in the `5xx` range indicate an error with RaiseDonors servers (these are rare). There will also be informational messages in the body of the response when an error occurs, giving you non-sensitive information into the reason behind the error. # Connection timeouts A connection timeout occurs when the network socket connection fails before you send or receive data. Connection timeouts are usually more manageable than stream timeouts because you know there is a problem right away. High network latency, high server load, saturation, or blockages on our remote server can lead to connectivity timeouts. You can edit timeout values as needed in your own development code, but we typically recommend keeping the values low. For example, you might set the connection timeout as high as 60 seconds, but even that may be higher than necessary in most normal scenarios. # Downtime RaiseDonors’s API has a 99.9% uptime. We are rarely offline for planned maintenance. If we do have downtime, we will tweet information from @RaiseDonors and usually send an email. # Change log | Date | Description | | --- | --- | | July 9, 2021 | Add credit card expiration field as required to Donation endpoints. | | April 28, 2021 | Add support for donations submitted through API to trigger CRM integrations. | | Mar 24, 2021 | Add support for custom data items in a donation. A new element "CustomDataItems" is available. | | Feb 23, 2021 | Add support for donation.IsAnonymous. Add support for fund allocations to include a comment. | | Jan 8, 2021 | [Depricate donation endpoints](#17002270-aa7d-4065-88a2-bfcdcc1a9e2c), moving them to one large ["search" donation endpoint](#10340101-a417-44e2-9f2f-78dd390716d9). | | Aug 26, 2020 | Depricate Campaigns v1 endpoint. Introduce new "product" features and endpoints. | | Jul 15, 2020 | Add search capability to donors for null/empty crm keys. And for searching multiple meta key/values at once across funds. | | Jun 15, 2020 | Add isDeleted parameter for donation endpoints. | | May 28, 2020 | Schedule and donation endpoints now support admin feature to move objects to different donors. | | May 16, 2020 | API now follows settings for Country ISO and State ISO specifications | | Mar 3, 2020 | Create new endpoint for public querying of funds | | Feb 28, 2020 | Turn on rate limiting. Fix bug with "amount" vs "amountInCents" for recurring schedule endpoints. Introduce new endpoints to manage recurring schedules (delete & edit). | | Jan 31, 2020 | Reorganize layout of endpoints. Add new donation endpoints. | | Dec 12, 2019 | Add V2 Campaign endpoints | | Nov 24, 2019 | Add new public endpoints for summarized data |
Keywords this site has no keywords
IP-Adresses  52.206.105.62 (more) (US)
34.237.153.113 (more) (US)
54.146.91.68 (more) (US)
   

Headerinformations

Connection close
Server nginx
Vary Accept-Encoding
Content-Length 60701
Content-Type text/html; charset=utf-8
Access-Control-Allow-Credentials true
Access-Control-Allow-Origin https://phs.getpostman.com
Access-Control-Expose-Headers 
Content-Security-Policy font-src 'self' *.getpostman.com documenter.postman.com fonts.gstatic.com fonts.googleapis.com *.pstmn.io; frame-ancestors 'none'; img-src * data:; script-src 'self' 'unsafe-inline' 'strict-dynamic' *.getpostman.com documenter.postman.com documenter-assets.pstmn.io content.pstmn.io run.pstmn.io https://cdn.ravenjs.com 'nonce-te5wIlxUw+QDZ2eCc6ipCXSS64CEUWAjU+tzglENs2hpvqdh'; style-src 'self' 'unsafe-inline' *.getpostman.com documenter.postman.com *.pstmn.io fonts.gstatic.com fonts.googleapis.com
Referrer-Policy no-referrer-when-downgrade
Strict-Transport-Security max-age=31536000; includeSubDomains
X-Content-Security-Policy font-src 'self' *.getpostman.com documenter.postman.com fonts.gstatic.com fonts.googleapis.com *.pstmn.io; frame-ancestors 'none'; img-src * data:; script-src 'self' 'unsafe-inline' 'strict-dynamic' *.getpostman.com documenter.postman.com documenter-assets.pstmn.io content.pstmn.io run.pstmn.io https://cdn.ravenjs.com 'nonce-te5wIlxUw+QDZ2eCc6ipCXSS64CEUWAjU+tzglENs2hpvqdh'; style-src 'self' 'unsafe-inline' *.getpostman.com documenter.postman.com *.pstmn.io fonts.gstatic.com fonts.googleapis.com
X-Content-Type-Options nosniff
X-Frame-Options DENY
X-Meta-Charset utf-8
X-Meta-Collection-Info-Public true
X-Meta-Collection-IsPublicCollection false
X-Meta-CollectionId 4090760-acdbfecd-eed4-4925-9266-a37f802b2193
X-Meta-DocumentationLayout classic-double-column
X-Meta-EnvironmentUID 4090760-97dcfe7e-873c-442b-bc35-6e4fff9e3431
X-Meta-Generator Postman Documenter
X-Meta-Highlight EF5B25
X-Meta-IsEnvFetchError false
X-Meta-Languages [{"key":"csharp","label":"C#","variant":"HttpClient"},{"key":"csharp","label":"C#","variant":"RestSharp"},{"key":"curl","label":"cURL","variant":"cURL"},{"key":"dart","label":"Dart","variant":"http"},{"key":"go","label":"Go","variant":"Native"},{"key":"http","label":"HTTP","variant":"HTTP"},{"key":"java","label":"Java","variant":"OkHttp"},{"key":"java","label":"Java","variant":"Unirest"},{"key":"javascript","label":"JavaScript","variant":"Fetch"},{"key":"javascript","label":"JavaScript","variant":"jQuery"},{"key":"javascript","label":"JavaScript","variant":"XHR"},{"key":"c","label":"C","variant":"libcurl"},{"key":"nodejs","label":"NodeJs","variant":"Axios"},{"key":"nodejs","label":"NodeJs","variant":"Native"},{"key":"nodejs","label":"NodeJs","variant":"Request"},{"key":"nodejs","label":"NodeJs","variant":"Unirest"},{"key":"objective-c","label":"Objective-C","variant":"NSURLSession"},{"key":"ocaml","label":"OCaml","variant":"Cohttp"},{"key":"php","label":"PHP","variant":"cURL"},{"key":"php","label":"PHP","variant":"Guzzle"},{"key":"php","label":"PHP","variant":"HTTP_Request2"},{"key":"php","label":"PHP","variant":"pecl_http"},{"key":"powershell","label":"PowerShell","variant":"RestMethod"},{"key":"python","label":"Python","variant":"http.client"},{"key":"python","label":"Python","variant":"Requests"},{"key":"r","label":"R","variant":"httr"},{"key":"r","label":"R","variant":"RCurl"},{"key":"ruby","label":"Ruby","variant":"Net::HTTP"},{"key":"shell","label":"Shell","variant":"Httpie"},{"key":"shell","label":"Shell","variant":"wget"},{"key":"swift","label":"Swift","variant":"URLSession"}]
X-Meta-Logo https://res.cloudinary.com/postman/image/upload/t_team_logo_pubdoc/v1/team/ed23408b9f5d10b3bfb15037f6296ee4d7a00277faebd3fb94c01d69d60e7da6
X-Meta-OwnerId 4090760
X-Meta-PublishedId Uz5FLHSp
X-Meta-Right-Sidebar 303030
X-Meta-Run-Js https://run.pstmn.io/button.js
X-Meta-Top-Bar FFFFFF
X-Meta-Twitter-Card summary
X-Meta-Twitter-Data1 ?
X-Meta-Twitter-Domain ?
X-Meta-Twitter-Image https://res.cloudinary.com/postman/image/upload/t_team_logo_pubdoc/v1/team/ed23408b9f5d10b3bfb15037f6296ee4d7a00277faebd3fb94c01d69d60e7da6
X-Meta-Twitter-Label1 ?
X-Meta-VersionTagId latest
X-Meta-Viewport width=device-width,initial-scale=1
X-Srv-Span v=1;s=2fa0d3c36716bb73
X-Srv-Trace v=1;t=1e4255820ea40e15
X-UA-Compatible IE=edge
X-Webkit-Csp font-src 'self' *.getpostman.com documenter.postman.com fonts.gstatic.com fonts.googleapis.com *.pstmn.io; frame-ancestors 'none'; img-src * data:; script-src 'self' 'unsafe-inline' 'strict-dynamic' *.getpostman.com documenter.postman.com documenter-assets.pstmn.io content.pstmn.io run.pstmn.io https://cdn.ravenjs.com 'nonce-te5wIlxUw+QDZ2eCc6ipCXSS64CEUWAjU+tzglENs2hpvqdh'; style-src 'self' 'unsafe-inline' *.getpostman.com documenter.postman.com *.pstmn.io fonts.gstatic.com fonts.googleapis.com
X-Xss-Protection 1; mode=block
   

DNS-Informations

Rootdomain-DNS-Server  clyde.ns.cloudflare.com (more)
linda.ns.cloudflare.com (more)
 

Miscellaneous

last update 31.05.2022 16:21:34
Illegal data? Report illegal data >HERE<
 
getHPinfo.com dissociates itself from any content on the website docs.raisedonors.com. The content is the sole responsibility of the operator. getHPinfo.com has no influence on the content of docs.raisedonors.com. getHPinfo.com only shows publicly freely accessible data here.
IMPRINT PRIVACY POLICY
###INFOLINKS1###