Libraries tagged by contactus
raman/contact
7 Downloads
This is test package with contact us form
p.eraghi/first-package
2 Downloads
contact us form for laravel
omh/laracontact
5 Downloads
A Contact Us form for Laravel application
omer/contact
3 Downloads
Magento 2 module improve contact us module
magan/feedback
21 Downloads
This package helps to create quick contact-us form and send email to the admin.
lakm/contact
12 Downloads
A Laravel package provide full Contact-Us functionality for your website with full front-end scaffolding
jarir-ahmed/form-generator
3 Downloads
A package to generate reusable login, registration, and contact us forms in PHP.
iibs/arnm-contact
91 Downloads
Araneum's contact us bundle
golpik/contact
3 Downloads
Basic package to setup contact us form, it will send email as well save inquiry to db
dominicwatts/contacttodb
1 Downloads
Magento 2 plugin to store contact us form submission to database
dominicwatts/contactcc
21 Downloads
Email Copy To and BCC option in admin for contact us form
discussio/raas
665 Downloads
With this RESTful API you can integrate a global reward or incentive program into your app or platform. If you have any questions or if you'd like to receive your own credentials, please contact us at [email protected].
dhanphe/contact
3 Downloads
Contact us page
atul/contact-form
4 Downloads
This will be a contact us from for any project
alissonlinneker/statuspage-php-sdk
1 Downloads
# Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact # Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit and the request has been rejected. # Basics ## HTTPS It's required ## URL Prefix In order to maintain version integrity into the future, the API is versioned. All calls currently begin with the following prefix: https://api.statuspage.io/v1/ ## RESTful Interface Wherever possible, the API seeks to implement repeatable patterns with logical, representative URLs and descriptive HTTP verbs. Below are some examples and conventions you will see throughout the documentation. * Collections are buckets: https://api.statuspage.io/v1/pages/asdf123/incidents.json * Elements have unique IDs: https://api.statuspage.io/v1/pages/asdf123/incidents/jklm456.json * GET will retrieve information about a collection/element * POST will create an element in a collection * PATCH will update a single element * PUT will replace a single element in a collection (rarely used) * DELETE will destroy a single element ## Sending Data Information can be sent in the body as form urlencoded or JSON, but make sure the Content-Type header matches the body structure or the server gremlins will be angry. All examples are provided in JSON format, however they can easily be converted to form encoding if required. Some examples of how to convert things are below: // JSON { "incident": { "name": "test incident", "components": ["8kbf7d35c070", "vtnh60py4yd7"] } } // Form Encoded (using curl as an example): curl -X POST https://api.statuspage.io/v1/example \ -d "incident[name]=test incident" \ -d "incident[components][]=8kbf7d35c070" \ -d "incident[components][]=vtnh60py4yd7" # Authentication