Introduction
Welcome to the GoRaise API! You can use our API to get information on various retailers, rates and users in our database.
We have language bindings in Shell, with PHP & Javascript coming soon! You can view code examples in the dark area to the right, and you can switch the programming language of the examples with the tabs in the top right.
This example API documentation page was created with Slate. Feel free to edit it and use it as a base for your own API’s documentation.
Authentication
To authorize, use this code:
# With shell, you can just pass the correct header with each request
curl "api_endpoint_here"
-H "ApiKey: your_api_key"
Make sure to replace
your_api_key
with your API key.
GoRaise uses API keys to allow access to the API. You can request a new GoRaise API key by contacting our API team.
GoRaise expects for the API key to be included in all API requests to the server in a header that looks like the following:
ApiKey: your_api_key
Retailers
Get All Retailers
curl "https://rest.goraise.co.uk/retailers"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"total": 2703,
"per_page": 100,
"current_page": 1,
"last_page": 28,
"next_page_url": "https://rest.goraise.co.uk/retailers?page=2",
"prev_page_url": null,
"from": 1,
"to": 100,
"data": [
{
"id": 84,
"name": "Guernsey Travel",
"description": null,
"logo": null,
"terms": null,
"website_url": "www.guernseytravel.com",
"donation": null,
"shopping_url": "https://www.goraise.co.uk/go/guernseytravel?user_id="
},
{
"id": 85,
"name": "Tickettree.com",
"description": null,
"logo": null,
"terms": null,
"website_url": "www.tickettree.com",
"donation": null,
"shopping_url": "https://www.goraise.co.uk/go/tickettreecom?user_id="
}
]
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<total>2703</total>
<per_page>100</per_page>
<current_page>1</current_page>
<last_page>28</last_page>
<next_page_url>https://rest.goraise.co.uk/retailers?format=xml&page=2</next_page_url>
<prev_page_url/>
<from>1</from>
<to>100</to>
<data>
<datum>
<id>102</id>
<name>Yellow Moon</name>
<description>The Yellow Moon website offers hundreds of great toys, educational games, craft and seasonal products for your family to create, learn and have fun. There's FREE UK mainland delivery on all orders over £50.</description>
<logo>/images/retailers/logos/yellowmoon.png</logo>
<terms>Donations may only apply to the sale price and not include VAT, delivery and other such costs. Please do not use voucher codes from other websites as this may affect your donation.</terms>
<website_url>www.yellowmoon.org.uk</website_url>
<donation>1%</donation>
<shopping_url>https://www.goraise.co.uk/go/yellowmoon?user_id=</shopping_url>
</datum>
<datum>
<id>109</id>
<name>Zavvi</name>
<description>Enjoy a huge selection of entertainment including market leading prices on the latest release Games, accessories and console bundles. Not to mention a huge selection of music, film and more.</description>
<logo>/images/retailers/logos/zavvi.png</logo>
<terms>Donations may only apply to the sale price and not include VAT, delivery and other such costs. Please do not use voucher codes from other websites as this may affect your donation.</terms>
<website_url>www.zavvi.com</website_url>
<donation>3%</donation>
<shopping_url>https://www.goraise.co.uk/go/zavvi?user_id=</shopping_url>
</datum>
</datum>
</data>
</xml>
This endpoint retrieves all retailers.
HTTP Request
GET https://rest.goraise.co.uk/retailers
Query Parameters
| Parameter | Default | Description |
|---|---|---|
| per_page | 100 | How many results to pull back in one go. Can range from 10-250 |
| page | 1 | The paginated page of results you wish to view, as limited by the per_page variable |
| order_by | id | How the results should be ordered |
Get a Specific Retailer
curl "https://rest.goraise.co.uk/retailers/102"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 102,
"name": "Yellow Moon",
"description": "The Yellow Moon website offers hundreds of great toys, educational games, craft and seasonal products for your family to create, learn and have fun. There's FREE UK mainland delivery on all orders over £50.",
"logo": "images/retailers/logos/yellowmoon.png",
"terms": "Donations may only apply to the sale price and not include VAT, delivery and other such costs. Please do not use voucher codes from other websites as this may affect your donation.",
"website_url": "www.yellowmoon.org.uk",
"donation": "1%",
"shopping_url": "https://www.goraise.co.uk/go/yellowmoon?user_id="
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>102</id>
<name>Yellow Moon</name>
<description>The Yellow Moon website offers hundreds of great toys, educational games, craft and seasonal products for your family to create, learn and have fun. There's FREE UK mainland delivery on all orders over £50.</description>
<logo>/images/retailers/logos/yellowmoon.png</logo>
<terms>Donations may only apply to the sale price and not include VAT, delivery and other such costs. Please do not use voucher codes from other websites as this may affect your donation.</terms>
<website_url>www.yellowmoon.org.uk</website_url>
<donation>1%</donation>
<shopping_url>https://www.goraise.co.uk/go/yellowmoon?user_id=</shopping_url>
</xml>
This endpoint retrieves a specific retailer.
HTTP Request
GET https://rest.goraise.co.uk/retailers/<ID>
URL Parameters
| Parameter | Description |
|---|---|
| ID | The ID of the retailer to retrieve |
Users
Get All Users
curl "https://rest.goraise.co.uk/users"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"total": 1889,
"per_page": 100,
"current_page": 1,
"last_page": 19,
"next_page_url": "https://rest.goraise.co.uk/users?page=2",
"prev_page_url": null,
"from": 1,
"to": 100,
"data": [
{
"id": 1,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
]
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<total>1889</total>
<per_page>100</per_page>
<current_page>1</current_page>
<last_page>19</last_page>
<next_page_url>https://rest.goraise.co.uk/users?format=xml&page=2</next_page_url>
<prev_page_url/>
<from>1</from>
<to>100</to>
<data>
<datum>
<id>8</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</datum>
</datum>
</data>
</xml>
This endpoint retrieves all users.
HTTP Request
GET https://rest.goraise.co.uk/users
Query Parameters
| Parameter | Default | Description |
|---|---|---|
| per_page | 100 | How many results to pull back in one go. Can range from 10-250 |
| page | 1 | The paginated page of results you wish to view, as limited by the per_page variable |
| order_by | id | How the results should be ordered |
Get a Specific User
curl "https://rest.goraise.co.uk/users/8"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 8,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>8</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</xml>
This endpoint retrieves a specific user.
HTTP Request
GET https://rest.goraise.co.uk/users/<ID>
URL Parameters
| Parameter | Description |
|---|---|
| ID | The unique ID of the user |
Create a New User
curl "https://rest.goraise.co.uk/users"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X POST
-d<EMAIL_ADDRESS>The above command returns JSON structured like this:
{
"email"<EMAIL_ADDRESS>"id": 99
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<EMAIL_ADDRESS><id>99</id>
</xml>
This endpoint creates and returns a new user.
HTTP Request
POST https://rest.goraise.co.uk/users
Required Parameters
| Parameter | Description |
|---|---|
| The unique email address of the new user | |
| PASSWORD | The password of the user. Must be 6 characters or more |
Additional Optional Parameters
| Parameter | Description |
|---|---|
| FIRST_NAME | The user’s first name |
| LAST_NAME | The user’s surname |
| ADDRESS1 | The first line of the user’s address |
| POSTCODE | The user’s postal code |
Update a User
curl "https://rest.goraise.co.uk/users/99"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X PUT
-d "first_name=Gary&last_name=Garside"
The above command returns JSON structured like this:
{
"id": 99,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>99</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</xml>
This endpoint creates and returns a new user.
HTTP Request
PUT https://rest.goraise.co.uk/users/<ID>
Required Parameters
| Parameter | Description |
|---|---|
| ID | The unique ID of the user |
Updatable Attributes
| Parameter | Description |
|---|---|
| The user’s email address. Must be a valid email | |
| PASSWORD | Must be 6 characters long |
| FIRST_NAME | The user’s first name |
| LAST_NAME | The user’s surname |
| ADDRESS1 | The first line of the user’s address |
| POSTCODE | The user’s postal code |
Causes
Get All Causes
curl "https://rest.goraise.co.uk/causes"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"total": 427,
"per_page": 100,
"current_page": 1,
"last_page": 5,
"next_page_url": "https://rest.goraise.co.uk/causes?page=2",
"prev_page_url": null,
"from": 1,
"to": 100,
"data": [
{
"id": 51,
"name": "Gary's Soccer Club",
"description": "
Help us raise funds for the Gary's Soccer club, a Sunday league side trying to make enough funds to build the new club house
",
"address1": "",
"postcode": "",
"admins": [
{
"id": 38,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
],
"supporters": [
{
"id": 37,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
]
}
]
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<total>427</total>
<per_page>100</per_page>
<current_page>1</current_page>
<last_page>5</last_page>
<next_page_url>https://rest.goraise.co.uk/causes?format=xml&page=2</next_page_url>
<prev_page_url/>
<from>1</from>
<to>100</to>
<data>
<datum>
<id>51</id>
<name>Gary's Soccer Club</name>
<description>
Help us raise funds for the Gary's Soccer club, a Sunday league side trying to make enough funds to build the new club house
</description>
<address1/>
<postcode/>
<admins/>
<supporters>
<supporter>
<id>37</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</supporter>
<supporter>
<id>38</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</supporter>
</supporters>
</datum>
</data>
</xml>
This endpoint retrieves all causes.
HTTP Request
GET https://rest.goraise.co.uk/causes
Query Parameters
| Parameter | Default | Description |
|---|---|---|
| per_page | 100 | How many results to pull back in one go. Can range from 10-250 |
| page | 1 | The paginated page of results you wish to view, as limited by the per_page variable |
| order_by | id | How the results should be ordered |
Get a Specific Cause
curl "https://rest.goraise.co.uk/causes/51"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 51,
"name": "Gary's Soccer Club",
"description": "
Help us raise funds for the Gary's Soccer club, a Sunday league side trying to make enough funds to build the new club house
",
"address1": "",
"postcode": "",
"admins": [
{
"id": 38,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
],
"supporters": [
{
"id": 37,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
]
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>51</id>
<name>Gary's Soccer Club</name>
<description>
Help us raise funds for the Gary's Soccer club, a Sunday league side trying to make enough funds to build the new club house
</description>
<address1/>
<postcode/>
<admins/>
<supporters>
<supporter>
<id>37</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</supporter>
<supporter>
<id>38</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</supporter>
</supporters>
</xml>
This endpoint retrieves a specific cause.
HTTP Request
GET https://rest.goraise.co.uk/causes/<ID>
URL Parameters
| Parameter | Description |
|---|---|
| ID | The unique ID of the cause |
Create a New Cause
curl "https://rest.goraise.co.uk/causes"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X POST
-d "name=NSPCC&description=Some information about the NSPCC&charity_number=123457680"
The above command returns JSON structured like this:
{
"name": "NSPCC",
"description": "Some information about the NSPCC",
"charity_number": "123457680",
"id": 75919
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<name>NSPCC</name>
<description>Some information about the NSPCC</description>
<charity_number>123457680</charity_number>
<id>75919</id>
</xml>
This endpoint creates and returns a new cause.
HTTP Request
POST https://rest.goraise.co.uk/causes
Required Parameters
| Parameter | Description |
|---|---|
| NAME | The name of the good cause |
Additional Attributes
| Parameter | Description |
|---|---|
| DESCRIPTION | Detailed description about the cause |
| ADDRESS1 | The first line of the cause’s address |
| POSTCODE | The cause’s postal code |
| CHARITY_NUMBER | The registered charity number of the cause, if applicable |
Update a Cause
curl "https://rest.goraise.co.uk/causes/75919"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X PUT
-d "name=NSPCB&description=Updating the NSPCB description"
The above command returns JSON structured like this:
{
"id": 75919,
"name": "NSPCB",
"description": "Updating the NSPCB description",
"charity_number": "123457680",
"address1": null,
"postcode": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>75919</id>
<name>NSPCB</name>
<description>Updating the NSPCB description</description>
<charity_number>123457680</charity_number>
<address1/>
<postcode/>
</xml>
This endpoint updates and returns a cause with a specific ID.
HTTP Request
PUT https://rest.goraise.co.uk/causes/<ID>
Required Parameters
| Parameter | Description |
|---|---|
| ID | The unique ID of the cause |
Updatable Attributes
| Parameter | Description |
|---|---|
| NAME | The name of the cause |
| DESCRIPTION | Detailed description about the cause |
| ADDRESS1 | The first line of the cause’s address |
| POSTCODE | The cause’s postal code |
| CHARITY_NUMBER | The registered charity number of the cause, if applicable |
Companies
Get All Companies
curl "https://rest.goraise.co.uk/companies"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"total": 427,
"per_page": 100,
"current_page": 1,
"last_page": 5,
"next_page_url": "https://rest.goraise.co.uk/companies?page=2",
"prev_page_url": null,
"from": 1,
"to": 100,
"data": [
{
"id": 1,
"name": "GoRaise",
"description": "Raise money for a good cause every time you shop online",
"address1": "",
"postcode": "",
"admins": [
{
"id": 38,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
],
"supporters": [
{
"id": 37,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
]
}
]
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<total>427</total>
<per_page>100</per_page>
<current_page>1</current_page>
<last_page>5</last_page>
<next_page_url>https://rest.goraise.co.uk/companies?format=xml&page=2</next_page_url>
<prev_page_url/>
<from>1</from>
<to>100</to>
<data>
<datum>
<id>1</id>
<name>GoRaise</name>
<description>Raise money for a good cause every time you shop online</description>
<address1/>
<postcode/>
<admins/>
<supporters>
<supporter>
<id>37</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</supporter>
<supporter>
<id>38</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</supporter>
</supporters>
</datum>
</data>
</xml>
This endpoint retrieves all companies.
HTTP Request
GET https://rest.goraise.co.uk/companies
Query Parameters
| Parameter | Default | Description |
|---|---|---|
| per_page | 100 | How many results to pull back in one go. Can range from 10-250 |
| page | 1 | The paginated page of results you wish to view, as limited by the per_page variable |
| order_by | id | How the results should be ordered |
Get a Specific Company
curl "https://rest.goraise.co.uk/companies/1"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 1,
"name": "GoRaise",
"description": "Raise money for a good cause every time you shop online",
"address1": "",
"postcode": "",
"admins": [
{
"id": 38,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
],
"supporters": [
{
"id": 37,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
]
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>1</id>
<name>GoRaise</name>
<description>Raise money for a good cause every time you shop online</description>
<address1/>
<postcode/>
<admins/>
<supporters>
<supporter>
<id>37</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</supporter>
<supporter>
<id>38</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</supporter>
</supporters>
</xml>
This endpoint retrieves a specific company.
HTTP Request
GET https://rest.goraise.co.uk/companies/<ID>
URL Parameters
| Parameter | Description |
|---|---|
| ID | The unique ID of the company |
Create a New Company
curl "https://rest.goraise.co.uk/companies"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X POST
-d "name=NSPCC&description=Some information about the NSPCC&charity_number=123457680"
The above command returns JSON structured like this:
{
"name": "NSPCC",
"description": "Some information about the NSPCC",
"charity_number": "123457680",
"id": 75919
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<name>NSPCC</name>
<description>Some information about the NSPCC</description>
<charity_number>123457680</charity_number>
<id>75919</id>
</xml>
This endpoint creates and returns a new company.
HTTP Request
POST https://rest.goraise.co.uk/companies
Required Parameters
| Parameter | Description |
|---|---|
| NAME | The name of the good company |
Additional Attributes
| Parameter | Description |
|---|---|
| DESCRIPTION | Detailed description about the company |
| ADDRESS1 | The first line of the company’s address |
| POSTCODE | The company’s postal code |
| CHARITY_NUMBER | The registered charity number of the company, if applicable |
Update a Company
curl "https://rest.goraise.co.uk/companies/1"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X PUT
-d "name=GoRaise&description=Updating the GoRaise description"
The above command returns JSON structured like this:
{
"id": 1,
"name": "GoRaise",
"description": "Updating the GoRaise description",
"charity_number": "123457680",
"address1": null,
"postcode": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>1</id>
<name>GoRaise</name>
<description>Updating the GoRaise description</description>
<charity_number>123457680</charity_number>
<address1/>
<postcode/>
</xml>
This endpoint updates and returns a company with a specific ID.
HTTP Request
PUT https://rest.goraise.co.uk/companies/<ID>
Required Parameters
| Parameter | Description |
|---|---|
| ID | The unique ID of the company |
Updatable Attributes
| Parameter | Description |
|---|---|
| NAME | The name of the company |
| DESCRIPTION | Detailed description about the company |
| ADDRESS1 | The first line of the company’s address |
| POSTCODE | The company’s postal code |
| CHARITY_NUMBER | The registered charity number of the company, if applicable |
Challengers
Get All Challengers
curl "https://rest.goraise.co.uk/challengers"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"total": 427,
"per_page": 100,
"current_page": 1,
"last_page": 5,
"next_page_url": "https://rest.goraise.co.uk/challengers?page=2",
"prev_page_url": null,
"from": 1,
"to": 100,
"data": [
{
"id": 1,
"name": "Gary's Everest Climb",
"description": "Raising money for NSPCC by climbing Mt. Everest!",
"address1": "",
"postcode": "",
"admins": [
{
"id": 38,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
],
"supporters": [
{
"id": 37,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
]
}
]
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<total>427</total>
<per_page>100</per_page>
<current_page>1</current_page>
<last_page>5</last_page>
<next_page_url>https://rest.goraise.co.uk/challengers?format=xml&page=2</next_page_url>
<prev_page_url/>
<from>1</from>
<to>100</to>
<data>
<datum>
<id>1</id>
<name>Gary's Everest Climb</name>
<description>Raising money for NSPCC by climbing Mt. Everest!</description>
<address1/>
<postcode/>
<admins/>
<supporters>
<supporter>
<id>37</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</supporter>
<supporter>
<id>38</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</supporter>
</supporters>
</datum>
</data>
</xml>
This endpoint retrieves all challengers.
HTTP Request
GET https://rest.goraise.co.uk/challengers
Query Parameters
| Parameter | Default | Description |
|---|---|---|
| per_page | 100 | How many results to pull back in one go. Can range from 10-250 |
| page | 1 | The paginated page of results you wish to view, as limited by the per_page variable |
| order_by | id | How the results should be ordered |
Get a Specific Challenger
curl "https://rest.goraise.co.uk/challengers/1"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 1,
"name": "Gary's Everest Climb",
"description": "Raising money for NSPCC by climbing Mt. Everest!",
"address1": "",
"postcode": "",
"admins": [
{
"id": 38,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
],
"supporters": [
{
"id": 37,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": null,
"postcode": null
}
]
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>1</id>
<name>Gary's Everest Climb</name>
<description>Raising money for NSPCC by climbing Mt. Everest!</description>
<address1/>
<postcode/>
<admins/>
<supporters>
<supporter>
<id>37</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</supporter>
<supporter>
<id>38</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</supporter>
</supporters>
</xml>
This endpoint retrieves a specific challenger.
HTTP Request
GET https://rest.goraise.co.uk/challengers/<ID>
URL Parameters
| Parameter | Description |
|---|---|
| ID | The unique ID of the challenger |
Create a New Challenger
curl "https://rest.goraise.co.uk/challengers"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X POST
-d "name=Everest Climb&description=Some information about the climb"
The above command returns JSON structured like this:
{
"name": "Everest Climb",
"description": "Some information about the climb",
"id": 75919
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<name>Everest Climb</name>
<description>Some information about the climb</description>
<id>75919</id>
</xml>
This endpoint creates and returns a new challenger.
HTTP Request
POST https://rest.goraise.co.uk/challengers
Required Parameters
| Parameter | Description |
|---|---|
| NAME | The name of the good challenger |
Additional Attributes
| Parameter | Description |
|---|---|
| DESCRIPTION | Detailed description about the challenger |
| ADDRESS1 | The first line of the challenger’s address |
| POSTCODE | The challenger’s postal code |
| CHARITY_NUMBER | The registered charity number of the challenger, if applicable |
Update a Challenger
curl "https://rest.goraise.co.uk/challengers/75919"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X PUT
-d "name=Climb&description=Updating the climb description"
The above command returns JSON structured like this:
{
"id": 75919,
"name": "Climb",
"description": "Updating the climb description",
"address1": null,
"postcode": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>75919</id>
<name>Climb</name>
<description>Updating the climb description</description>
<address1/>
<postcode/>
</xml>
This endpoint updates and returns a challenger with a specific ID.
HTTP Request
PUT https://rest.goraise.co.uk/challengers/<ID>
Required Parameters
| Parameter | Description |
|---|---|
| ID | The unique ID of the challenger |
Updatable Attributes
| Parameter | Description |
|---|---|
| NAME | The name of the challenger |
| DESCRIPTION | Detailed description about the challenger |
| ADDRESS1 | The first line of the challenger’s address |
| POSTCODE | The challenger’s postal code |
| CHARITY_NUMBER | The registered charity number of the challenger, if applicable |
Clicks
Get All Clicks
curl "https://rest.goraise.co.uk/clicks"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"total": 6372,
"per_page": 100,
"current_page": 1,
"last_page": 64,
"next_page_url": "https://rest.goraise.co.uk/clicks?page=2",
"prev_page_url": null,
"from": 1,
"to": 100,
"data": [
{
"id": 1,
"timestamp": "2015-04-01 09:58:24",
"retailer": {
"id": 331,
"name": "O2 Mobile Broadband",
"description": null,
"logo": null,
"terms": null,
"website_url": "shop.o2.co.uk",
"donation": null
},
"user": {
"id": 1,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": "",
"postcode": ""
}
}
]
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<total>6372</total>
<per_page>100</per_page>
<current_page>1</current_page>
<last_page>64</last_page>
<next_page_url>https://rest.goraise.co.uk/clicks?format=xml&page=2</next_page_url>
<prev_page_url/>
<from>1</from>
<to>100</to>
<data>
<datum>
<id>1</id>
<timestamp>2015-04-01 09:58:24</timestamp>
<retailer>
<id>331</id>
<name>O2 Mobile Broadband</name>
<description/>
<logo/>
<terms/>
<website_url>shop.o2.co.uk</website_url>
<donation/>
</retailer>
<user>
<id>1</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</user>
</datum>
</data>
</xml>
This endpoint retrieves all clicks.
HTTP Request
GET https://rest.goraise.co.uk/clicks
Query Parameters
| Parameter | Default | Description |
|---|---|---|
| per_page | 100 | How many results to pull back in one go. Can range from 10-250 |
| page | 1 | The paginated page of results you wish to view, as limited by the per_page variable |
| order_by | id | How the results should be ordered |
Get a Specific Click
curl "https://rest.goraise.co.uk/clicks/1"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 1,
"timestamp": "2015-04-01 09:58:24",
"retailer": {
"id": 331,
"name": "O2 Mobile Broadband",
"description": null,
"logo": null,
"terms": null,
"website_url": "shop.o2.co.uk",
"donation": null
},
"user": {
"id": 1,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": "",
"postcode": ""
}
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>1</id>
<timestamp>2015-04-01 09:58:24</timestamp>
<retailer>
<id>331</id>
<name>O2 Mobile Broadband</name>
<description/>
<logo/>
<terms/>
<website_url>shop.o2.co.uk</website_url>
<donation/>
</retailer>
<user>
<id>1</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</user>
</xml>
This endpoint retrieves a specific click.
HTTP Request
GET https://rest.goraise.co.uk/clicks/<ID>
URL Parameters
| Parameter | Description |
|---|---|
| ID | The unique ID of the click |
Transactions
Get All Transactions
curl "https://rest.goraise.co.uk/transactions"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"total": 1087,
"per_page": 100,
"current_page": 1,
"last_page": 11,
"next_page_url": "https://rest.goraise.co.uk/transactions?page=2",
"prev_page_url": null,
"from": 1,
"to": 100,
"data": [
{
"id": 2996,
"revenue": "9.99",
"donation": "0.30",
"retailer": {
"id": 109,
"name": "Zavvi",
"description": "Enjoy a huge selection of entertainment including market leading prices on the latest release Games, accessories and console bundles. Not to mention a huge selection of music, film and more.",
"logo": "images/retailers/logos/zavvi.png",
"terms": "Donations may only apply to the sale price and not include VAT, delivery and other such costs. Please do not use voucher codes from other websites as this may affect your donation.",
"website_url": "www.zavvi.com",
"donation": "3%"
},
"click": {
"id": 17,
"timestamp": "2015-04-01 12:22:21",
"user": {
"id": 7,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": "",
"postcode": ""
}
}
}
]
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<total>1087</total>
<per_page>100</per_page>
<current_page>1</current_page>
<last_page>11</last_page>
<next_page_url>https://rest.goraise.co.uk/transactions?format=xml&page=2</next_page_url>
<prev_page_url/>
<from>1</from>
<to>100</to>
<data>
<datum>
<id>2996</id>
<revenue>9.99</revenue>
<donation>0.30</donation>
<retailer>
<id>109</id>
<name>Zavvi</name>
<description>Enjoy a huge selection of entertainment including market leading prices on the latest release Games, accessories and console bundles. Not to mention a huge selection of music, film and more.</description>
<logo>/images/retailers/logos/zavvi.png</logo>
<terms>Donations may only apply to the sale price and not include VAT, delivery and other such costs. Please do not use voucher codes from other websites as this may affect your donation.</terms>
<website_url>www.zavvi.com</website_url>
<donation>3%</donation>
</retailer>
<click>
<id>17</id>
<timestamp>2015-04-01 12:22:21</timestamp>
<user>
<id>7</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</user>
</click>
</datum>
</data>
</xml>
This endpoint retrieves all transactions.
HTTP Request
GET https://rest.goraise.co.uk/transactions
Query Parameters
| Parameter | Default | Description |
|---|---|---|
| per_page | 100 | How many results to pull back in one go. Can range from 10-250 |
| page | 1 | The paginated page of results you wish to view, as limited by the per_page variable |
| order_by | id | How the results should be ordered |
Get a Specific Transaction
curl "https://rest.goraise.co.uk/transactions/1"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 2996,
"revenue": "9.99",
"donation": "0.30",
"retailer": {
"id": 109,
"name": "Zavvi",
"description": "Enjoy a huge selection of entertainment including market leading prices on the latest release Games, accessories and console bundles. Not to mention a huge selection of music, film and more.",
"logo": "images/retailers/logos/zavvi.png",
"terms": "Donations may only apply to the sale price and not include VAT, delivery and other such costs. Please do not use voucher codes from other websites as this may affect your donation.",
"website_url": "www.zavvi.com",
"donation": "3%"
},
"click": {
"id": 17,
"timestamp": "2015-04-01 12:22:21",
"user": {
"id": 7,
"first_name": "Gary",
"last_name": "Garside",
"email"<EMAIL_ADDRESS>"address1": "",
"postcode": ""
}
}
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>2996</id>
<revenue>9.99</revenue>
<donation>0.30</donation>
<retailer>
<id>109</id>
<name>Zavvi</name>
<description>Enjoy a huge selection of entertainment including market leading prices on the latest release Games, accessories and console bundles. Not to mention a huge selection of music, film and more.</description>
<logo>/images/retailers/logos/zavvi.png</logo>
<terms>Donations may only apply to the sale price and not include VAT, delivery and other such costs. Please do not use voucher codes from other websites as this may affect your donation.</terms>
<website_url>www.zavvi.com</website_url>
<donation>3%</donation>
</retailer>
<click>
<id>17</id>
<timestamp>2015-04-01 12:22:21</timestamp>
<user>
<id>7</id>
<first_name>Gary</first_name>
<last_name>Garside</last_name>
<EMAIL_ADDRESS><address1/>
<postcode/>
</user>
</click>
</xml>
This endpoint retrieves a specific transaction.
HTTP Request
GET https://rest.goraise.co.uk/transactions/<ID>
URL Parameters
| Parameter | Description |
|---|---|
| ID | The unique ID of the transaction |
Payments
Get All Payments
curl "https://rest.goraise.co.uk/payments"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 37,
"groups_payment_details_id": 474,
"amount": 47.19,
"notes": "Created payment for Leicester Speedway Supporters Club",
"created_at": "2016-04-11 12:27:26",
"updated_at": "2016-04-11 12:27:26",
"paid_at": null,
"status": "pending",
"transaction_groups": [
{
"id": 5171,
"percentage": 100,
"value": 0.51,
"historical": 0,
"transaction": {
"id": 3758,
"revenue": "102.00",
"donation": "0.51"
}
},
]
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<total>26</total>
<per_page>100</per_page>
<current_page>1</current_page>
<last_page>1</last_page>
<next_page_url/>
<prev_page_url/>
<from>1</from>
<to>26</to>
<data>
<datum>
<id>21</id>
<groups_payment_details_id>112</groups_payment_details_id>
<amount>366.64</amount>
<notes>Created payment for Friends of Salusbury School</notes>
<created_at>2016-01-22 10:34:07</created_at>
<updated_at>2016-01-22 11:48:06</updated_at>
<paid_at>2016-01-22 11:48:06</paid_at>
<status>paid</status>
<transaction_groups>
<transaction_group>
<id>23</id>
<percentage>100</percentage>
<value>4.62</value>
<historical>0</historical>
<transaction>
<id>3012</id>
<revenue>369.00</revenue>
<donation>4.62</donation>
</transaction>
</transaction_group>
</transaction_groups>
</datum>
</data>
</xml>
This endpoint retrieves all payments.
HTTP Request
GET https://rest.goraise.co.uk/payments
Query Parameters
| Parameter | Default | Description |
|---|---|---|
| per_page | 100 | How many results to pull back in one go. Can range from 10-250 |
| page | 1 | The paginated page of results you wish to view, as limited by the per_page variable |
| order_by | id | How the results should be ordered |
Get a Specific Payment
curl "https://rest.goraise.co.uk/payments/1"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 37,
"groups_payment_details_id": 474,
"amount": 47.19,
"notes": "Created payment for Leicester Speedway Supporters Club",
"created_at": "2016-04-11 12:27:26",
"updated_at": "2016-04-11 12:27:26",
"paid_at": null,
"status": "pending",
"transaction_groups": [
{
"id": 5171,
"percentage": 100,
"value": 0.51,
"historical": 0,
"transaction": {
"id": 3758,
"revenue": "102.00",
"donation": "0.51"
}
},
]
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>21</id>
<groups_payment_details_id>112</groups_payment_details_id>
<amount>366.64</amount>
<notes>Created payment for Friends of Salusbury School</notes>
<created_at>2016-01-22 10:34:07</created_at>
<updated_at>2016-01-22 11:48:06</updated_at>
<paid_at>2016-01-22 11:48:06</paid_at>
<status>paid</status>
<transaction_groups>
<transaction_group>
<id>23</id>
<percentage>100</percentage>
<value>4.62</value>
<historical>0</historical>
<transaction>
<id>3012</id>
<revenue>369.00</revenue>
<donation>4.62</donation>
</transaction>
</transaction_group>
</transaction_groups>
</xml>
This endpoint retrieves a specific payment.
HTTP Request
GET https://rest.goraise.co.uk/payments/<ID>
URL Parameters
| Parameter | Description |
|---|---|
| ID | The unique ID of the payment |
Cause Payment Details
Get All Cause Payment Details
curl "https://rest.goraise.co.uk/causes/75911/payment-details"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 131801,
"type": "cheque",
"active": 0,
"groups_id": 75911,
"minimum_payment": 22,
"paypal_email": "",
"bank_acc_name": "",
"bank_acc_number": null,
"bank_acc_sort": "",
"use_company_address": 1,
"provider": "test",
"payment_url": null,
"payment_url_protocol": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<item>
<id>131801</id>
<type>cheque</type>
<active>0</active>
<groups_id>75911</groups_id>
<minimum_payment>22</minimum_payment>
<paypal_email/>
<bank_acc_name/>
<bank_acc_number/>
<bank_acc_sort/>
<use_company_address>1</use_company_address>
<provider>test</provider>
<payment_url/>
<payment_url_protocol/>
</item>
</xml>
This endpoint retrieves a list all payment details for a cause.
HTTP Request
GET https://rest.goraise.co.uk/causes/<CAUSE_ID>/payment-details
URL Parameters
| Parameter | Description |
|---|---|
| CAUSE_ID | The id of the cause. |
Get a Specific Payment Detail
curl "https://rest.goraise.co.uk/causes/75911/payment-details/131801"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 131805,
"type": "thirdparty",
"active": 1,
"groups_id": 75423,
"minimum_payment": 15.5,
"paypal_email": "",
"bank_acc_name": "",
"bank_acc_number": null,
"bank_acc_sort": "",
"use_company_address": 1,
"provider": null,
"payment_url": null,
"payment_url_protocol": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>131805</id>
<type>thirdparty</type>
<active>1</active>
<groups_id>75423</groups_id>
<minimum_payment>15.5</minimum_payment>
<paypal_email/>
<bank_acc_name/>
<bank_acc_number/>
<bank_acc_sort/>
<use_company_address>1</use_company_address>
<provider/>
<payment_url/>
<payment_url_protocol/>
</xml>
This endpoint retrieves a specific set of payment details
HTTP Request
GET https://rest.goraise.co.uk/causes/<CAUSE_ID>/payment-details/<ID>
URL Parameters
| Parameter | Description |
|---|---|
| CAUSE_ID | The id of the cause. |
| ID | The unique ID of the payment details item. |
Create a New Cause Payment Details Entry
curl "https://rest.goraise.co.uk/causes/75423/payment-details"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X POST
-d "type=cheque&minimium_payment=16.00"
The above command returns JSON structured like this:
{
"type": "cheque",
"minimum_payment": "16.00",
"groups_id": 75423,
"id": 131806
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<type>cheque</type>
<minimum_payment>16.00</minimum_payment>
<groups_id>75423</groups_id>
<id>131807</id>
</xml>
This endpoint creates and returns a payment detail item for a specified cause.
HTTP Request
POST https://rest.goraise.co.uk/causes/<CAUSE_ID>/payment-details
URL Structure
| Parameter | Description |
|---|---|
| CAUSE_ID | The id of the cause. |
Required Parameters
| Parameter | Description |
|---|---|
| TYPE | Type of payment, [cheque,bank_account,thirdparty] |
| MINIMUM_PAYMENT | The minimum payout threshold. |
Additional Attributes
| Parameter | Description |
|---|---|
| PAYPAL_EMAIL | The email of the associated paypal account (if applicable). |
| BANK_ACC_NAME | The bank account name (if applicable). |
| BANK_ACC_NUMBER | The bank account number (if applicable). |
| BANK_ACC_SORT | The bank account sort code (if applicable). |
| USE_COMPANY_ADDRESS | Whether or not to use the company address for the payment detail. |
| PROVIDER | The provider name (if applicable). |
| PAYMENT_URL | The URL the payment method, minus the protocol. e.g. www.justgiving.com/cancerresearchuk |
| PAYMENT_URL_PROTOCOL | The protocol of the URL, e.g. https:// or http:// |
Update a Cause Payment Detail
curl "PUT https://rest.goraise.co.uk/causes/75911/payment-details/131801"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X PUT
-d "type=cheque&minimium_payment=16.00"
The above command returns JSON structured like this:
{
"id": 131801,
"type": "cheque",
"active": 0,
"groups_id": 75911,
"minimum_payment": 22,
"paypal_email": "",
"bank_acc_name": "",
"bank_acc_number": null,
"bank_acc_sort": "",
"use_company_address": 1,
"provider": "test",
"payment_url": null,
"payment_url_protocol": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<item>
<id>131801</id>
<type>cheque</type>
<active>0</active>
<groups_id>75911</groups_id>
<minimum_payment>22</minimum_payment>
<paypal_email/>
<bank_acc_name/>
<bank_acc_number/>
<bank_acc_sort/>
<use_company_address>1</use_company_address>
<provider>test</provider>
<payment_url/>
<payment_url_protocol/>
</item>
</xml>
This endpoint updates and returns a cause payment detail with a specific ID.
HTTP Request
PUT https://rest.goraise.co.uk/causes/<ID>
URL Structure
| Parameter | Description |
|---|---|
| CAUSE_ID | The id of the cause. |
Required Parameters
| Parameter | Description |
|---|---|
| TYPE | Type of payment, [cheque,bank_account,thirdparty] |
| MINIMUM_PAYMENT | The minimum payout threshold. |
Additional Attributes
| Parameter | Description |
|---|---|
| PAYPAL_EMAIL | The email of the associated paypal account (if applicable). |
| BANK_ACC_NAME | The bank account name (if applicable). |
| BANK_ACC_NUMBER | The bank account number (if applicable). |
| BANK_ACC_SORT | The bank account sort code (if applicable). |
| USE_COMPANY_ADDRESS | Whether or not to use the company address for the payment detail. |
| PROVIDER | The provider name (if applicable). |
| PAYMENT_URL | The URL the payment method, minus the protocol. e.g. www.justgiving.com/cancerresearchuk |
| PAYMENT_URL_PROTOCOL | The protocol of the URL, e.g. https:// or http:// |
Company Payment Details
Get All Company Payment Details
curl "https://rest.goraise.co.uk/companies/75911/payment-details"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 131801,
"type": "cheque",
"active": 0,
"groups_id": 75911,
"minimum_payment": 22,
"paypal_email": "",
"bank_acc_name": "",
"bank_acc_number": null,
"bank_acc_sort": "",
"use_company_address": 1,
"provider": "test",
"payment_url": null,
"payment_url_protocol": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<item>
<id>131801</id>
<type>cheque</type>
<active>0</active>
<groups_id>75911</groups_id>
<minimum_payment>22</minimum_payment>
<paypal_email/>
<bank_acc_name/>
<bank_acc_number/>
<bank_acc_sort/>
<use_company_address>1</use_company_address>
<provider>test</provider>
<payment_url/>
<payment_url_protocol/>
</item>
</xml>
This endpoint retrieves a list all payment details for a company
HTTP Request
GET https://rest.goraise.co.uk/companies/<COMPANY_ID>/payment-details
URL Parameters
| Parameter | Description |
|---|---|
| COMPANY_ID | The id of the company |
Get a Specific Payment Detail
curl "https://rest.goraise.co.uk/companies/75911/payment-details/131801"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 131805,
"type": "thirdparty",
"active": 1,
"groups_id": 75423,
"minimum_payment": 15.5,
"paypal_email": "",
"bank_acc_name": "",
"bank_acc_number": null,
"bank_acc_sort": "",
"use_company_address": 1,
"provider": null,
"payment_url": null,
"payment_url_protocol": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>131805</id>
<type>thirdparty</type>
<active>1</active>
<groups_id>75423</groups_id>
<minimum_payment>15.5</minimum_payment>
<paypal_email/>
<bank_acc_name/>
<bank_acc_number/>
<bank_acc_sort/>
<use_company_address>1</use_company_address>
<provider/>
<payment_url/>
<payment_url_protocol/>
</xml>
This endpoint retrieves a specific set of payment details
HTTP Request
GET https://rest.goraise.co.uk/companies/<COMPANY_ID>/payment-details/<ID>
URL Parameters
| Parameter | Description |
|---|---|
| COMPANY_ID | The id of the company |
| ID | The unique ID of the payment details item |
Create a New Company Payment Details Entry
curl "https://rest.goraise.co.uk/companies/75423/payment-details"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X POST
-d "type=cheque&minimium_payment=16.00"
The above command returns JSON structured like this:
{
"type": "cheque",
"minimum_payment": "16.00",
"groups_id": 75423,
"id": 131806
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<type>cheque</type>
<minimum_payment>16.00</minimum_payment>
<groups_id>75423</groups_id>
<id>131807</id>
</xml>
This endpoint creates and returns a payment detail item for a specified company
HTTP Request
POST https://rest.goraise.co.uk/companies/<COMPANY_ID>/payment-details
URL Structure
| Parameter | Description |
|---|---|
| COMPANY_ID | The id of the company |
Required Parameters
| Parameter | Description |
|---|---|
| TYPE | Type of payment, [cheque,bank_account,thirdparty] |
| MINIMUM_PAYMENT | The minimum payout threshold. |
Additional Attributes
| Parameter | Description |
|---|---|
| PAYPAL_EMAIL | The email of the associated paypal account (if applicable). |
| BANK_ACC_NAME | The bank account name (if applicable). |
| BANK_ACC_NUMBER | The bank account number (if applicable). |
| BANK_ACC_SORT | The bank account sort code (if applicable). |
| USE_COMPANY_ADDRESS | Whether or not to use the company address for the payment detail. |
| PROVIDER | The provider name (if applicable). |
| PAYMENT_URL | The URL the payment method, minus the protocol. e.g. www.justgiving.com/cancerresearchuk |
| PAYMENT_URL_PROTOCOL | The protocol of the URL, e.g. https:// or http:// |
Update a Company Payment Detail
curl "PUT https://rest.goraise.co.uk/companies/75911/payment-details/131801"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X PUT
-d "type=cheque&minimium_payment=16.00"
The above command returns JSON structured like this:
{
"id": 131801,
"type": "cheque",
"active": 0,
"groups_id": 75911,
"minimum_payment": 22,
"paypal_email": "",
"bank_acc_name": "",
"bank_acc_number": null,
"bank_acc_sort": "",
"use_company_address": 1,
"provider": "test",
"payment_url": null,
"payment_url_protocol": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<item>
<id>131801</id>
<type>cheque</type>
<active>0</active>
<groups_id>75911</groups_id>
<minimum_payment>22</minimum_payment>
<paypal_email/>
<bank_acc_name/>
<bank_acc_number/>
<bank_acc_sort/>
<use_company_address>1</use_company_address>
<provider>test</provider>
<payment_url/>
<payment_url_protocol/>
</item>
</xml>
This endpoint updates and returns a cause payment detail with a specific ID.
HTTP Request
PUT https://rest.goraise.co.uk/companies/<ID>
URL Structure
| Parameter | Description |
|---|---|
| COMPANY_ID | The id of the company |
Required Parameters
| Parameter | Description |
|---|---|
| TYPE | Type of payment, [cheque,bank_account,thirdparty] |
| MINIMUM_PAYMENT | The minimum payout threshold. |
Additional Attributes
| Parameter | Description |
|---|---|
| PAYPAL_EMAIL | The email of the associated paypal account (if applicable). |
| BANK_ACC_NAME | The bank account name (if applicable). |
| BANK_ACC_NUMBER | The bank account number (if applicable). |
| BANK_ACC_SORT | The bank account sort code (if applicable). |
| USE_COMPANY_ADDRESS | Whether or not to use the company address for the payment detail. |
| PROVIDER | The provider name (if applicable). |
| PAYMENT_URL | The URL the payment method, minus the protocol. e.g. www.justgiving.com/cancerresearchuk |
| PAYMENT_URL_PROTOCOL | The protocol of the URL, e.g. https:// or http:// |
Challenger Payment Details
Get All Challenger Payment Details
curl "https://rest.goraise.co.uk/challengers/75911/payment-details"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 131801,
"type": "cheque",
"active": 0,
"groups_id": 75911,
"minimum_payment": 22,
"paypal_email": "",
"bank_acc_name": "",
"bank_acc_number": null,
"bank_acc_sort": "",
"use_company_address": 1,
"provider": "test",
"payment_url": null,
"payment_url_protocol": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<item>
<id>131801</id>
<type>cheque</type>
<active>0</active>
<groups_id>75911</groups_id>
<minimum_payment>22</minimum_payment>
<paypal_email/>
<bank_acc_name/>
<bank_acc_number/>
<bank_acc_sort/>
<use_company_address>1</use_company_address>
<provider>test</provider>
<payment_url/>
<payment_url_protocol/>
</item>
</xml>
This endpoint retrieves a list all payment details for a challenger
HTTP Request
GET https://rest.goraise.co.uk/challengers/<CHALLENGER_ID>/payment-details
URL Parameters
| Parameter | Description |
|---|---|
| CHALLENGER_ID | The id of the challenger |
Get a Specific Payment Detail
curl "https://rest.goraise.co.uk/challengers/75911/payment-details/131801"
-H "ApiKey: your_api_key"
The above command returns JSON structured like this:
{
"id": 131805,
"type": "thirdparty",
"active": 1,
"groups_id": 75423,
"minimum_payment": 15.5,
"paypal_email": "",
"bank_acc_name": "",
"bank_acc_number": null,
"bank_acc_sort": "",
"use_company_address": 1,
"provider": null,
"payment_url": null,
"payment_url_protocol": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<id>131805</id>
<type>thirdparty</type>
<active>1</active>
<groups_id>75423</groups_id>
<minimum_payment>15.5</minimum_payment>
<paypal_email/>
<bank_acc_name/>
<bank_acc_number/>
<bank_acc_sort/>
<use_company_address>1</use_company_address>
<provider/>
<payment_url/>
<payment_url_protocol/>
</xml>
This endpoint retrieves a specific set of payment details
HTTP Request
GET https://rest.goraise.co.uk/challengers/<CHALLENGER_ID>/payment-details/<ID>
URL Parameters
| Parameter | Description |
|---|---|
| CHALLENGER_ID | The id of the challenger |
| ID | The unique ID of the payment details item |
Create a New Challenger Payment Details Entry
curl "https://rest.goraise.co.uk/challengers/75423/payment-details"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X POST
-d "type=cheque&minimium_payment=16.00"
The above command returns JSON structured like this:
{
"type": "cheque",
"minimum_payment": "16.00",
"groups_id": 75423,
"id": 131806
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<type>cheque</type>
<minimum_payment>16.00</minimum_payment>
<groups_id>75423</groups_id>
<id>131807</id>
</xml>
This endpoint creates and returns a payment detail item for a specified challenger
HTTP Request
POST https://rest.goraise.co.uk/challengers/<CHALLENGER_ID>/payment-details
URL Structure
| Parameter | Description |
|---|---|
| CHALLENGER_ID | The id of the challenger |
Required Parameters
| Parameter | Description |
|---|---|
| TYPE | Type of payment, [cheque,bank_account,thirdparty] |
| MINIMUM_PAYMENT | The minimum payout threshold. |
Additional Attributes
| Parameter | Description |
|---|---|
| PAYPAL_EMAIL | The email of the associated paypal account (if applicable). |
| BANK_ACC_NAME | The bank account name (if applicable). |
| BANK_ACC_NUMBER | The bank account number (if applicable). |
| BANK_ACC_SORT | The bank account sort code (if applicable). |
| USE_COMPANY_ADDRESS | Whether or not to use the company address for the payment detail. |
| PROVIDER | The provider name (if applicable). |
| PAYMENT_URL | The URL the payment method, minus the protocol. e.g. www.justgiving.com/cancerresearchuk |
| PAYMENT_URL_PROTOCOL | The protocol of the URL, e.g. https:// or http:// |
Update a Challenger Payment Detail
curl "PUT https://rest.goraise.co.uk/challengers/75911/payment-details/131801"
-H "ApiKey: your_api_key"
-H "Content-Type: application/x-www-form-urlencoded"
-X PUT
-d "type=cheque&minimium_payment=16.00"
The above command returns JSON structured like this:
{
"id": 131801,
"type": "cheque",
"active": 0,
"groups_id": 75911,
"minimum_payment": 22,
"paypal_email": "",
"bank_acc_name": "",
"bank_acc_number": null,
"bank_acc_sort": "",
"use_company_address": 1,
"provider": "test",
"payment_url": null,
"payment_url_protocol": null
}
The above command returns XML structured like this:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<item>
<id>131801</id>
<type>cheque</type>
<active>0</active>
<groups_id>75911</groups_id>
<minimum_payment>22</minimum_payment>
<paypal_email/>
<bank_acc_name/>
<bank_acc_number/>
<bank_acc_sort/>
<use_company_address>1</use_company_address>
<provider>test</provider>
<payment_url/>
<payment_url_protocol/>
</item>
</xml>
This endpoint updates and returns a cause payment detail with a specific ID.
HTTP Request
PUT https://rest.goraise.co.uk/causes/<ID>
URL Structure
| Parameter | Description |
|---|---|
| CHALLENGER_ID | The id of the challenger |
Required Parameters
| Parameter | Description |
|---|---|
| TYPE | Type of payment, [cheque,bank_account,thirdparty] |
| MINIMUM_PAYMENT | The minimum payout threshold |
Additional Attributes
| Parameter | Description |
|---|---|
| PAYPAL_EMAIL | The email of the associated paypal account (if applicable). |
| BANK_ACC_NAME | The bank account name (if applicable). |
| BANK_ACC_NUMBER | The bank account number (if applicable). |
| BANK_ACC_SORT | The bank account sort code (if applicable). |
| USE_COMPANY_ADDRESS | Whether or not to use the company address for the payment detail. |
| PROVIDER | The provider name (if applicable). |
| PAYMENT_URL | The URL the payment method, minus the protocol. e.g. www.justgiving.com/cancerresearchuk |
| PAYMENT_URL_PROTOCOL | The protocol of the URL, e.g. https:// or http:// |
Errors
The GoRaise API uses the following error codes:
| Error Code | Meaning |
|---|---|
| 400 | Bad Request – Your request sucks |
| 401 | Unauthorized – Your API key is wrong |
| 403 | Forbidden – The data requested is hidden for administrators only |
| 404 | Not Found – The specified data could not be found |
| 405 | Method Not Allowed – You tried to access data with an invalid method |
| 406 | Not Acceptable – You requested a format that isn’t offered |
| 410 | Gone – The data requested has been removed from our servers |
| 418 | I’m a teapot |
| 429 | Too Many Requests – You’re requesting too much data! Slow down! |
| 500 | Internal Server Error – We had a problem with our server. Try again later. |
| 503 | Service Unavailable – We’re temporarially offline for maintanance. Please try again later. |


Files CCore/inc/task/NoMutex.h CCore/src/task/NoMutex.cpp
NoMutex is a class with the Mutex interface, but with empty methods. It is required sometimes to create a class, which can be used either in a single-threaded context or in a multi-threaded. This class can be implemented as a template, parametrized by a mutex type to avoid using a real mutex if it is not required.
class NoMutex : NoCopy
{
public:
NoMutex() {}
explicit NoMutex(TextLabel) {}
~NoMutex() {}
void lock() {}
void unlock() {}
struct Lock : NoCopy
{
explicit Lock(NoMutex &) {}
};
};


BaronTheDev
BaronTheDev
Home
My Services
About Me
Work
Certificate
Responsive Web Design
FreeCodeCamp
My 300 coursework certificate of proof!


Kyber Network Announces Strategic Partnership with Enigma
“Besides serving as an exchange, Kyber Network also provides payment APIs that will allow wallet accounts to easily receive payments from any crypto tokens.”
KyberNetwork announces a partnership with Enigma to reinforce both companies’ commitment to help others realize the full potential of a decentralized economy. Enigma seeks to enable the scalability of blockchains by providing a complementary off-chain data network, where larger quantities of information can be securely shared and processed without incurring severe on-chain costs.
Earlier this week, Kyber Network issued a progress report which detailed a timeline that the team will comply to. Kyber Network has stated that it is still on track to its mainnet launch in February next year, and will create an ecosystem of partnerships to support the platform.
As a start, the partnership between the two companies will center around Catalyst, Enigma’s first product. Primarily, Catalyst will be used to support reserve operators on Kyber Network, while Kyber Network will integrate with Catalyst as a data provider and as an exchange service. In the longer term, both companies will work towards their shared vision for the decentralization of crypto-asset exchange and the expansion of blockchains through numerous other potential initiatives.
When asked about the collaboration, Kyber Network CEO Loi Luu commented “our partnership with Enigma solidifies our aspiration to be the leader in the crypto-asset exchange sector. With Enigma’s vision, their deep understanding of blockchain technology and the power of Catalyst, this collaboration is expected to spark innovation and additional research into the intricacies of trading behavior. In so doing, we hope that our efforts can close the gap between data demand and supply, and empower effective and efficient use of data.”
“All of us at Enigma have tremendous respect for the Kyber Network team and their vision for the future of decentralization.” said Guy Zyskind, CEO and co-founder of Enigma. “Our companies are excited to work towards future strategic initiatives and believe this sets a strong precedent for our other partnerships in the space.”
About Kyber Network
Kyber Network is an on-chain protocol which allows instant exchange and conversion of digital assets (e.g. crypto tokens) and cryptocurrencies (e.g. Ether, Bitcoin, ZCash) with guaranteed liquidity. Kyber Network will be the first system that implements several ideal operating properties of an exchange including trustless, decentralized execution, instant trade and high liquidity. Besides serving as an exchange, Kyber Network also provides payment APIs that will allow wallet accounts to easily receive payments from any crypto tokens.
About Enigma
Enigma is creating a decentralized data marketplace protocol to revolutionize the way data is shared, aggregated and monetized. Enigma seeks to enable the scalability of blockchains by providing a complementary off-chain data network, where larger quantities of information can be securely shared and processed without incurring severe on-chain costs. Enigma’s first product to be built on the Enigma protocol is Catalyst, which connects crypto traders and investors with the data critical to creating their edge in the crypto markets and provides them with backtesting, research, and execution tools. Enigma’s goal is to build protocols and products that revolutionize data sharing in the same way Bitcoin has revolutionized payments.
「 Declaration: Please indicate the source if repost the article in UNITIMES. Opinions expressed by Contributors belong to themselves. 」


labeled
by Kevin Reiss at 2023-02-24 22:06:55.renamed
by Kevin Reiss at 2023-02-24 22:37:38.head_ref_force_pushed
by None at 2023-02-24 22:15:29.ready_for_review
by None at 2023-02-24 22:30:52.referenced
by Kevin Reiss at 2023-02-24 22:33:27.merged
by Kevin Reiss at 2023-02-24 22:33:27.closed
by Kevin Reiss at 2023-02-24 22:33:27.head_ref_deleted
by Kevin Reiss at 2023-02-24 22:33:28.referenced
by Kevin Reiss at 2023-02-24 22:33:48.merged
by Kevin Reiss at 2023-02-24 22:33:48.closed
by Kevin Reiss at 2023-02-24 22:33:48.head_ref_deleted
by Kevin Reiss at 2023-02-24 22:33:49.referenced
by Kevin Reiss at 2023-02-24 22:34:26.merged
by Kevin Reiss at 2023-02-24 22:34:26.closed
by Kevin Reiss at 2023-02-24 22:34:27.head_ref_deleted
by Kevin Reiss at 2023-02-24 22:34:29.OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version
or @dependabot ignore this minor version
.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
closed
by Kevin Reiss at 2023-02-24 22:35:26.head_ref_deleted
by None at 2023-02-24 22:35:34.referenced
by Kevin Reiss at 2023-02-24 22:35:41.merged
by Kevin Reiss at 2023-02-24 22:35:41.closed
by Kevin Reiss at 2023-02-24 22:35:41.head_ref_deleted
by Kevin Reiss at 2023-02-24 22:35:42.labeled
by Kevin Reiss at 2023-02-24 22:12:40.Lewis would like to have the same renewal workflow for their lockers that Firestone uses.
Created issue to implement feature at https://github.com/pulibrary/lockers_and_study_spaces/issues/201
closed
by Kevin Reiss at 2023-02-24 22:13:11.closing in favor of #222
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version
or @dependabot ignore this minor version
.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
closed
by Jane Sandberg at 2023-02-24 22:51:03.head_ref_deleted
by None at 2023-02-24 22:51:12.closed
by Kevin Reiss at 2023-02-24 22:36:17.referenced
by Jane Sandberg at 2023-02-24 23:06:38.merged
by Jane Sandberg at 2023-02-24 23:06:38.closed
by Jane Sandberg at 2023-02-24 23:06:39.head_ref_deleted
by Jane Sandberg at 2023-02-24 23:06:40.labeled
by None at 2023-02-24 23:08:38.labeled
by None at 2023-02-24 23:08:38.labeled
by None at 2023-02-24 23:08:59.labeled
by None at 2023-02-24 23:08:59.referenced
by Jane Sandberg at 2023-02-24 23:15:12.merged
by Jane Sandberg at 2023-02-24 23:15:12.closed
by Jane Sandberg at 2023-02-24 23:15:12.head_ref_deleted
by Jane Sandberg at 2023-02-24 23:15:13.closed
by Jane Sandberg at 2023-02-24 23:15:14.referenced
by Jane Sandberg at 2023-02-24 23:15:14.referenced
by Jane Sandberg at 2023-02-24 23:16:51.merged
by Jane Sandberg at 2023-02-24 23:16:51.closed
by Jane Sandberg at 2023-02-24 23:16:52.head_ref_deleted
by Jane Sandberg at 2023-02-24 23:16:53.labeled
by None at 2023-02-24 23:18:27.labeled
by None at 2023-02-24 23:18:27.Superseded by #741.
closed
by None at 2023-02-24 23:18:31.head_ref_deleted
by None at 2023-02-24 23:18:32.labeled
by None at 2023-02-24 23:07:20.labeled
by None at 2023-02-24 23:07:20.head_ref_force_pushed
by None at 2023-02-24 23:16:07.head_ref_force_pushed
by None at 2023-02-24 23:18:34.referenced
by Jane Sandberg at 2023-02-24 23:18:55.merged
by Jane Sandberg at 2023-02-24 23:18:56.closed
by Jane Sandberg at 2023-02-24 23:18:56.head_ref_deleted
by Jane Sandberg at 2023-02-24 23:18:57.


public interface KbApiService extends CycApiEntryPoint
AssertionService getAssertionService()
BinaryPredicateService getBinaryPredicateService()
ContextService getContextService()
FactService getFactService()
FirstOrderCollectionService getFirstOrderCollectionService()
KbCollectionService getKbCollectionService()
KbFunctionService getKbFunctionService()
KbIndividualService getKbIndividualService()
KbPredicateService getKbPredicateService()
KbService getKbService()
KbTermService getKbTermService()
RelationService getRelationService()
RuleService getRuleService()
SecondOrderCollectionService getSecondOrderCollectionService()
SentenceService getSentenceService()
SymbolService getSymbolService()
VariableService getVariableService()
Copyright © 2015–2018 Cycorp, Inc. All rights reserved.


Email *
Nickname *
Password *
Email
Password
Copyright © 2016 All rights Reserved | Template by 梁非凡小组


JPC runs many different drama groups throughout the year. Currently the main extra curricular drama group is Spotlight which is held in the theatre after school on Thursdays. Here students can work on sharpening their acting skills and practise for upcoming drama assesmements. Spotlight doesn't require previous experiance and stundents are encouraged to come along to the practise times and see if it is something that they'd be interested in joining.


FAQ: Frequently Asked Questions
1. Installing and Updating
How do I update an existing installation?
As of taskpaper+ 0.7beta3 you can now just copy the new files over the top of the old ones. Your data folder and configuration will not be affected.
2. Editing
How can I add a new task or project using the edit-in-place box?
Double-click any task to begin editing in place, then simply type above or below the existing task and add a new one using the usual
- new tasksyntax. New projects and notes can also be added this way. In reality it's just a mini version of the big edit view.
Is it possible to adapt this list of filters in the right sidebar to your my preferences?
Yes, in the conf/lang_en.php file (look for your own language where this exists). Open the file in a real text editor (please do not use MS Word!)
Now look for the $lang['filter_settings']
array; each line contains the parameters for a filter.
The first item
is the filter expression, this can be any valid search expression,
exactly as you would type into the search box. Second is the tooltip
to be displayed, the third, the colour to use for the background.
Fourth is whether to make the filter visible or not (invisible ones can still be used from the Search Box. It's actually very easy to create new filters.
4. Navigating
Why doesn't the back button work? (FIXED)
Simple answer: I'm not clever enough yet to make it work correctly
Real problem: this is a so-called AJAX web application, the web page is only loaded once, the first time you start the app (or if you refresh the browser page). All other information is updated in-place on the page as needed, tabs, tasks, tags, and so on. So the actual page address does not change, so there's nowhere to go "back" to! I'm working on a solution but its slow in coming.
**NEW**: as on version 0.8alpha the back button now works as expected (thanks to jQuery jAddress plugin and a wholelot of programming to make it work in taskpaper.
Where are my taskpaper files saved?
Find where you put your Taskpaper+ installation folder, open it up and navigate to {taskpaper+ folder}\www\taskpaper\data\ and there you should see all your busy little plain-text files that contain all your tasks. You can edit these files directly with a text editor if you wish (please don't use Word! Download Notepad2 or Notepad++)
Note: the text files are in UTF-8 encoding with Unix LF line-endings which standard Windows Notepad doesn't handle so well, so a decent text editor is recommended. There's a plethora of really good free ones out there so no excuses! (e.g Notepad++, Notepad2, etc.. Google is your friend)
How do I sync, backup, import, or export my tasks?
Well, they're just plain-text files, so you can just save a copy of the entire data folder somewhere else, or use a good file sync or backup program to do it automatically (I recommend FreeFileSync, SyncToy or CobianBackup9 myself, but then YMMV). I personally use a version control system (Darcs) to keep revisions of my tasks.
If you really want to get clever you could sync the data folder via Dropbox on the web, or a similar service, to have you tasks available at work and home, either way its easy to work with good ol' plain-text
6. User Interface
Q. I'm sick of the tooltips, I know all the functions by heart now, so can I turn them off?
A. You'll be glad to know the answer is yes. Open the conf/config.php and change the $config['hide_tips] value to true. That's it, all tooltips will disappear!
Q. Can I change the interface to my own language, instead of English?
A. yes, it is possible. French is already provided, and if you are ready to translate the conf/lang_en.php into your own language you can easily use that too. Please send any translated lang_nn.php files to me and I will willingly add them to the program. The language selection can be made in the conf/config.ini file, by changing the language=en to the whatever language is available, e.g. french is language=fra.
7. Why can't... why isn't?
Why isn't the syntax exactly like Taskpaper from Hogbay?
I guess the best answer is 'personal preference.' I wrote this app initially for my own use (and still use it daily), and I changed a few symbols because I think they are more obvious and easier to use. A prime example is the use of 'X- closed task' rather than Hogbay's '- closed task @done
Ask yourself which one is quicker to write, easier to see, and easier to internationalise?
Q. Why do I have to dig into text files to change settings, why don't you provide a nice settings page like other programs?
A. Just a question of time, I haven't had time to write a settings page yet. It'll come one day! Remember I don't get paid for writing taskpaper, I do it because it's useful to me, and I enjoy it. Editing text files is not really that difficult though... ;-)
Symon Bent, South Africa. Revised: 26-Jun-2010 20:30


Welcome,
!
Profile
|
Logout
POLLS
OPTIONS
Poll:
New Poll!
Delete Poll!
Option:
New Option!
Delete Option!


--- layout: post status: publish published: true title: Podcast 4.53 - 42% More Troughs author: display_name: Corey Fineran login: Corey email<EMAIL_ADDRESS>url: '' author_login: Corey author_email<EMAIL_ADDRESS>wordpress_id: 8151 wordpress_url: http://ivyenvy.com/?p=8151 date: '2013-01-22 22:41:16 +0000' date_gmt: '2013-01-23 04:41:16 +0000' categories: - Management - Podcast tags: - Cubs Convention - Cubs Caravan - James Rowson - Cubs Convention 2013 - Cubs Caravan 2013 - Wrigley Field Renovation comments: [] ---
Andy, Corey and Jeremy are able to discuss a topic that many Cubs fans have been waiting for a long time - Wrigley Field is being renovated.
Cubs Caravan traveled to Peoria last Wednesday. Corey and Jeremy were there and Corey tells you why he thinks Cubs Caravan may not return to Peoria. Jeremy made the trip to Chicago for Cubs Convention and compares this year with previous Cubs Conventions.
As mentioned, the biggest news out of Cubs Convention this year was the announcement and details of the renovation of Wrigley Field. Andy describes all the Wrigley Field renovations, we read some listener feedback on the renovation and then we tell you what we think about it.
Corey had the opportunity to speak with Cubs hitting coach, James Rowson at the Cubs Caravan event in Peoria. Listen to Rowson's take on Soriano's surprise 2012 season and the struggles of Brett Jackson. We also hear what Rowson thinks about the guys in the minor league system.
In Kurt's absence, Andy steps up with the lone Cubs.com Internet Muscle Flex of the Week. We have started a Google+ Community and we'll now be posting our photos for the caption contests over there, as well as on Facebook.


Celebrating everything that is Lancashire in night of music, dialect and quizzes
A true celebration of the Red Rose county takes place on Friday at Fleetwood Bowling Club.
by Claire LarkLancashire Night is a celebration of music and dialect poetry with a Lancashire Quiz and hotpot supper.
The entertainers for the evening will be popular Lancashire folk musicans Mail Train, who feature guitars, banjo, bass and ukulele. Lead vocalist, Jan Hough, has been described as ‘mad as a box of frogs’ and backing them will be local entertainers, Mike Fairclough and Ian Brandwood and Jim Slater.Lancashire Day commemorates the day when the county first sent representatives to sit in Parliament in 1295. Tickets: (01253) 876621


Headers are the big, banner-like images that adorn the tops of pages. For your header to look its best on all devices, make sure anything important is located near the center of the image.
dash.forms.image_filetype_help_html
The recommended size for a header image is %{dimensions}
(ratio of 4 ÷ 1).
What are the header requirements and guidelines?


[gecode-users] Counting booleans
Malcolm Ryan
malcolmr at cse.unsw.edu.au
Thu Feb 14 06:55:55 CET 2008
Another question: I have two lists of variables X1 ... Xn and Y1 ...
Yn. I want to constrain them so that at most one (or exactly one) of
the Xi's differs from the corresponding Yi.
This is one of those things that would propagate better with a
specialised constraint. Does such a constraint exist (in Gecode/J)?
If we had booleans Bi = (Xi = Yi), this could be represented by a
constraint which said that at most (or exactly) one Bi was true. Does
such a constraint exist?
Malcolm
--
"If there is one thing worse than the modern weakening of major morals
it is the modern strengthening of minor morals.
Thus it is considered more withering to accuse a man
of bad taste than of bad ethics." -- G.K.Chesterton, On Lying
in Bed
More information about the gecode-users
mailing list


NBA docks Clippers US$50k for Rivers' Leonard injury comments
LOS ANGELES: The National Basketball Association has slapped the Los Angeles Clippers with a US$50,000 fine because of comments coach Doc Rivers made about Kawhi Leonard's injury status.
"The NBA has fined the Clippers US$50,000 for statements, including by head coach Doc Rivers, that were inconsistent with Leonard's health status," the league's disciplinary officials said in a statement on Thursday.
On Wednesday, the league said it accepted the Clippers decision to sit Leonard in the first of back-to-back games. The club's injury report listed Leonard as having a sore knee.
As a result, Leonard did not dress in a 129-124 loss to the Milwaukee Bucks.
The league then took issue with Rivers' description of the matter.
"I think Kawhi made a statement that he's never felt better. It's our job to make sure he stays that way. That's important. But he played a lot of minutes in the playoffs last year," Rivers said.
"So, it's not, uh, a health thing really. It is in some ways. We want him to just keep feeling better and getting better."
The league levied the fine but added in their statement they still believe Leonard has a legitimate injury.
"Following additional review of the LA Clippers not playing Kawhi Leonard in last night's game against the Milwaukee Bucks, the NBA has confirmed that the team's decision to sit Leonard for management of an injury was consistent with league rules," the statement read.
"The team has reasonably determined that Leonard is suffering from an ongoing injury to the patella tendon in his left knee and has been placed by the team at this time on an injury protocol for back-to-back games."
The Clippers hosted the Portland Trail Blazers on Thursday night, and Leonard was expected to play.
NBA rules prohibit teams from resting healthy players for high-profile, nationally televised games, with a fine of US$100,000 possible.


--- title: Scripting Languages tags: [ computers, languages, programming, scripting ] picture: technonerdmonster music: mood: didactic location: Somewhere in cyberspace layout: post posted: Thu Jul 26 17:46:18 PDT 2018 ---
Today in my continuing series on programming languages I'm going to talk about "scripting languages". "Scripting" is a rather fuzzy category, because unlike the kinds of languages we've discussed before, scripting languages are really distinguished by how they are used, and they're used in two very different ways. It's also confusing because most scripting languages are interpreted, and people tend to use "scripting" when they should be using "interpreted". In my opinion it's more correct to say that a language is being used as a scripting language, rather than to say that it is a scripting language. As we'll see, this is particularly true when the language is being used to customize some application.
But first, let's define scripts. A script is basically a sequence of commands that a user could type at a terminal[1] -- often called "the command line" -- that have been put together in a file so that they can be run automatically. The script then becomes a new command. In Linux, and before that Unix, the program that interprets user commands is called a "shell", possibly because it's the visible outer layer of the operating system. The quintessential script is a shell script. We'll dive into the details later.
[1] okay, a terminal emulator. Hardly anyone uses physical terminals
anymore. Or remembers that the "tty" in /dev/tty
stands for
"teletype"'.
The second kind of scripting language is used to implement commands inside some interactive program that isn't a shell. (These languages are also called extension languages, because they're extending the capabilities of their host program, or sometimes configuration languages.) Extension languages generally look nothing at all like something you'd type into a shell -- they're really just programming languages, and often are just the programming language the application was written in. The commands of an interactive program like a text editor or graphics editor tend to be things like single keystrokes and mouse gestures, and in most cases you wouldn't want to -- or even be able to -- write programs with them. I'll use "extension languages" for languages used in this way. There's some overlap in between, and I'll talk about that later.
Before there was Unix, there were mainframes. At first, you would punch out decks of Hollerith cards, hand them to the computer operator, and they would (eventually) put it in the reader and push the start button, and you would come back an hour or so later and pick up your deck with a pile of listings from the printer.
Computers were expensive in those days, so to save time the operator would pile a big batch of card decks on top of one another with a couple of "job control" cards in between to separate the jobs. Job control languages were really the first scripting languages. (And the old terminology lingers on, as such things do, in the ".bat" extension of MS/DOS (later Windows) "batch files". Which are shell scripts.)
By far the most sophisticated job control language ran on the Burroughs 5000 and 6000 series computers, which were designed to run Algol very efficiently. (So efficiently that they used Algol as what amounted to their assembly language! Programs in other languages, including Fortran and Cobol, were compiled by first translating them into Algol.) The job control language was a somewhat extended version of Algol in which some variables had files as their values, and programs were simply subroutines.
Side note: the Burroughs machines' operating system was called MCP, which stands for Master Control Program. Movie fans may find that name familiar.
Even DOS batch files had control-flow statements (conditionals and loops) and the ability to substitute variables into commands. But these features were clumsy to use. In contrast, the Unix shell written by Stephen Bourne at Bell Labs was designed as a scripting language. The syntax of the control structures was, in fact, derived from Algol 68, which introduced the "if...fi" and "do...done" syntax.
Bourne's shell was called sh
in Unix's characteristically
terse style. The version of Unix developed at Berkeley, (BSD, for
Berkeley System Distribution -- I'll talk about the history of operating
systems some time) had a shell called the C shell, csh
, which
had a syntax derived from the C programming language. That immediately
gave rise to the popular tongue-twister "she sells cshs by the cshore".
The GNU (GNU's Not Unix) project, started by Richard Stallman with the
goal of producing a completely free replacement for Unix, naturally had
its own rewrite of the Bourne Shell called bash
-- the Bourne
Again Shell. It's a considerable improvement over the original, pulling
in features from csh
and some other shell variants.
Let's look at shell scripting a little more closely. The basic statement is a command -- the name of a program followed by its arguments, just as you would type it on the command line. If the command isn't one of the few built-in ones, the shell then looks for a file that matches the name of the command, and runs it. The program eventually produces some output, and exits with a result code that indicates either success or failure.
There are a few really brilliant things going on here.
tee
that does both: copies
its input into a file, and also passes it along to the next command in
the pipeline.
true
that does nothing but immediately
returns success, and another called false
that immediately
fails. There's another one, test
, which can perform
various tests, for example to see whether two strings are equal, or a
file is writable. There's an alias for it: [
. Unix
allows all sorts of characters in filenames. Anyway, you can say
things like if [ -w $f ]; then...
today=`date`
takes the result of
running the date
program and puts it in a variable called
today
.
This is basically functional programming, with programs as functions and files as variables. (Of course, you can define variables and functions in the shell as well.) In case you were wondering whether Bash is a "real" programming language, take a look at nanoblogger and Abcde (A Better CD Encoder).
Sometime later in this series I'll devote a whole post to an introduction to shell scripting. For now, I'll just show you a couple of my favorite one-liners to give you a taste for it.  Note that comments in shell -- almost all Unix scripting languages, as a matter of fact -- start with an octothorpe. (I'll talk about octothorpe/sharp/hash/pound later, too.)
# wait until nova (my household server) comes back up after a reboot until ping -c1 nova; do sleep 10; done # count my blog posts. wc counts words, lines, and/or characters. find $HOME/.ljarchive -type f -print | wc -l # find all posts that were published in January. # grep prints lines in its input that match a pattern. find $HOME/.ljarchive -type f -print | grep /01/ | sort
As you can see, shell scripts tend to be a bit cryptic. That's partly
because shells are also meant to have commands typed at them directly, so
brevity is often favored over clarity. It's also because all of the
operations that work on files are programs in their own right;
they often have dozens of options and were written at different times by
different people. The find
program is often cited as a good
(or bad) example of this -- it has a very different set of options from
any other program, because you're trying to express a rather complicated
combination of tests on its command line.
Some things are just too complicated to express on a single line, at least
with anything resembling readability, so many other programs besides
shells are designed to run scripts. Some of the first of these in Unix
were sed
, the "stream editor", which applies text editing
operations to its input, and awk
, which splits lines into
"fields" and lets you do database-like operations on them. (Simpler
programs that also split lines into fields include sort
,
uniq
, and join
.)
DOS and Windows look at the last three characters of a program's name (e.g., "exe" for "executable" machine language and "bat" for "batch" scripts) to determine what it contains and how to run it. Unix, on the other hand, looks at the first few characters of the file itself. In particular, if these are "#!
" followed by the name of a program (I'm simplifying a little), the file is passed to that program to be run as a script. The "#!
" combination is usually pronounced "shebang". This accounts for the popularity of "#
" to mark comments -- lines that are meant to be ignored -- in most scripting languages.
The scripting programs we've seen so far -- sh
,
sed
, awk
, and some others -- are all designed to
do one kind of thing. Shells mostly just run commands, assign variables,
and substitute variables into commands, and rely on other programs like
find
and grep
to do most other things. Wouldn't
it be nice if one could combine all these functions into one program, and
give it a better language to write programs in. The first of these that
really took off was Larry Wall's Perl. Like the others it
allows you to put simple commands on the command line -- with exactly
the same syntax as grep and awk.
Perl's operations for searching and substituting text look just like the
ones in sed
and grep
. It has associative arrays
(basically lookup tables) just like the ones in awk
. It can
run programs and get their results exactly the way sh
does,
by enclosing them in backtick characters (`...` -- originally meant to be
used as left single quotes), and it can easily read lines out of files,
mess with them, and write them out. It has has objects, methods, and
(more or less) first-class functions. And just like find
and
the Unix command line, it has a well-earned reputation for scripts that
are obscure and hard to read.
You've probably heard Python mentioned. It was designed by Guido van Rossum in an attempt to be a better scripting language Perl, with an emphasis on making programs more readable, easier to write, and easier to maintain. He succeeded. At this point Python has mostly replaced Perl as the most popular scripting language, in addition to being a good first language for learning programming. (Which is the best language for learning is a subject guaranteed to invoke strong opinions and heated discussions; I'll avoid it for now.) I avoided Python for many years, but I'm finally learning it and finding it much better than I expected.
The other major kind of scripting is done to extend a program that isn't a shell. In most cases this will be an interactive program like an editor, but it doesn't have to be. Extensions of this sort may also be called "plugins".
Extension languages are usually small, simple, and interpreted, because nobody wants their text editor (for example) to include something as large and complex as a compiler when its main purpose is defining keyboard shortcuts. There's an exception to this -- sometimes when a program is written in a compiled language, the same language may be used for extensions. In that case the extensions have to be compiled in, which is usually inconvenient, but they can be particularly powerful. I've already written about one such case -- the Xmonad window manager, which is written and configured in Haskell.
Everyone these days has at least heard of JavaScript, which is the scripting language used in web pages. Like most scripting languages, JavaScript has escaped from its enclosure in the browser and run wild, to the point where text editors, whole web browsers, web servers, and so on are built in it.
Other popular extension languages include various kinds of Lisp, Tcl, and Lua. Lua and Tcl were explicitly designed to be embedded in programs. Lua is particularly popular in games, although it has recently turned up in other places, including the TeX typesetting system.
Lisp is an interesting case -- probably its earliest use as an extension language was in the Emacs text editor, which is almost entirely written in it. (To the point where many people say that it's a very good Lisp interpretor, but it needs a better text editor. I'm not one of them: I'm passionately fond of Emacs, and I'll write about it at greater length later on.) Because of its radically simple structure, Lisp is particularly easy to write an interpretor for. Emacs isn't the only example; there are Lisp variants in the Audacity audio workstation and the Autodesk CAD program. I used the one in Audacity for the sound effects in my computer/horror crossover song "Vampire Megabyte".
Emacs, Atom (a text editor written in JavaScript), and Xmonad are good examples of interactive programs where the same language is used for (most, if not all, of) the implementation as well as for the configuration files and the extensions. The boundaries can get very fuzzy in cases like that; as a Mandelbear I find that particularly appealing.


Click on an account name to to see more data about that account. Proof of concept for model-bound custom elements that use mustache.js to generate the view from that model.


Answer TRUE or FALSE.
Open hashing has the advantage that it can answer range queries or questions like what is the largest key in the database.
Hashing is good only for exact match queries.


Login
Forgot Password ?
LOGIN
Login with facebook
Create New Account
dashlab
Let’s Start The Journey
Enter the most beautiful admin ever