# Way to make salted api call within a package?

**URL:** <https://discourse.julialang.org/t/way-to-make-salted-api-call-within-a-package/9928>\
**Category:** General Usage\
**Tags:** question\
**Created:** [March 23, 2018, 6:05pm UTC](https://discourse.julialang.org/t/way-to-make-salted-api-call-within-a-package/9928 "2018-03-23T18:05:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [March 23, 2018, 7:33pm UTC](https://discourse.julialang.org/t/way-to-make-salted-api-call-within-a-package/9928/2 "2018-03-23T19:33:46Z")

</div>

> [@djsegal](#):
>
> \*using the nomenclature of: Distinguishing projects from packages

I’m not sure if it agrees or disagrees with your usage, but I’ve posted an update on the nomenclature that we’ve settled on in Pkg3:

> [@Distinguishing projects from packages](https://discourse.julialang.org/t/distinguishing-projects-from-packages/153/41):
>
> Update – terminology I ended up using in the Pkg3 documentation: [https://julialang.org/Pkg3.jl/latest/index.html#Glossary-1](https://julialang.org/Pkg3.jl/latest/index.html#Glossary-1) Quoting the relevant parts: Project: a source tree with a standard layout, including a src directory for the main body of Julia code, a test directory for testing the project, docs for documentation files, and optionally a build directory for a build script and its outputs. A project will typically also have a project file and may optionally have a manifest file: Pac…

---

_[View the full topic](https://discourse.julialang.org/t/way-to-make-salted-api-call-within-a-package/9928)._
