https://github.com/mixmaxhq/giphy-example-link-resolver
Giphy link resolver for Mixmax
https://github.com/mixmaxhq/giphy-example-link-resolver
example giphy mixmax
Last synced: 8 months ago
JSON representation
Giphy link resolver for Mixmax
- Host: GitHub
- URL: https://github.com/mixmaxhq/giphy-example-link-resolver
- Owner: mixmaxhq
- License: mit
- Created: 2015-10-11T18:13:16.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2023-08-10T17:39:35.000Z (almost 3 years ago)
- Last Synced: 2025-07-29T13:35:01.243Z (10 months ago)
- Topics: example, giphy, mixmax
- Language: JavaScript
- Homepage: http://sdk.mixmax.com
- Size: 11.7 KB
- Stars: 2
- Watchers: 3
- Forks: 10
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Giphy Link Preview for Mixmax
This is an open source Mixmax Link Resolver. See for more information about how to use this example code in Mixmax.
## Running locally
1. Install using `npm install`
2. Run using `npm start`
To simulate locally how Mixmax calls the resolver URL (to return HTML that goes into the email), run:
```
curl https://localhost:9146/resolver?url=http%3A%2F%2Fgiphy.com%2Fgifs%2Fexcited-the-office-yes-t3Mzdx0SA3Eis --insecure
```
## Why do we run it in https locally?
Mixmax slash command APIs are required to be served over https. This is because they are queried directly from the Mixmax client in the browser (using AJAX) that's running on an HTTPS domain. Browsers forbid AJAX requests from https domains to call http APIs, for security. So we must run an https server with a locally-signed certificate.
See [here](http://developer.mixmax.com/docs/integration-api-appendix#local-development-error-neterr_insecure_response) for how to fix the **ERR_INSECURE_RESPONSE** error that you might get in Chrome.